v0.4.5 more setup changes to get PyPI package in order

Author: sylikc

CHANGELOG.md

@@ -28,6 +28,7 @@ Date (Timezone)              | Version | Comment
 04/09/2020 04:25:31 AM (PDT) | 0.4.2   | roll back 0.4.0's pyexiftool rename.  It appears there's no specific PEP to have to to name PyPI projects to be py<something>.  The only convention I found was https://www.python.org/dev/peps/pep-0423/#use-standard-pattern-for-community-contributions which I might look at in more detail
 04/09/2020 05:15:40 AM (PDT) | 0.4.3   | initial work of moving the exiftool.py into a directory preparing to break it down into separate files to make the codebase more manageable
 03/12/2021 01:37:30 PM (PDT) | 0.4.4   | no functional code changes.  Revamped the setup.py and related files to release to PyPI.  Added all necessary and recommended files into release
+03/12/2021 02:03:38 PM (PDT) | 0.4.5   | no functional code changes.  re-release with new version because I accidentally included the "test" package with the PyPI 0.4.4 release.  I deleted it instead of yanking or doing a post release this time... just bumped the version.  "test" folder renamed to "tests" as per convention, so the build will automatically ignore it
 
 On version changes, update setup.py to reflect version
 

README.rst

@@ -65,7 +65,7 @@ Run tests to make sure it's functional
 
 ::
 
-    python -m unittest -v test/test_exiftool.py
+    python -m unittest -v tests/test_exiftool.py
 
 Documentation
 -------------

setup.py

@@ -30,7 +30,7 @@
 
 	# overview
 	name="PyExifTool",
-	version="0.4.4",
+	version="0.4.5",
 	license="GPLv3+/BSD",
 	url="http://github.com/sylikc/pyexiftool",
 	python_requires=">=2.6",
@@ -72,7 +72,12 @@
 		"Topic :: Multimedia",
 		"Topic :: Utilities",
 	],
-	packages=find_packages(where="."),
+	
+	
+	packages=find_packages(
+		where=".",
+		exclude = ['test*',]
+	),
 
 	#py_modules=["exiftool"], - it is now the exiftool module
 )