fix pip installation for Python < 3.6

Author: cs01

CHANGELOG.md

@@ -0,0 +1,3 @@
+0.1.2.1
+
+Fix installations for Python < 3.6 by adding environment marker to skip pipx (#9)

README.md

@@ -5,7 +5,7 @@
 </p>
 
 <a href="https://pypi.python.org/pypi/pythonloc/">
-<img src="https://img.shields.io/badge/pypi-0.1.2.0-blue.svg" /></a>
+<img src="https://img.shields.io/badge/pypi-0.1.2.1-blue.svg" /></a>
 
 **pythonloc** is a drop in replacement for `python` and `pip` that automatically recognizes a `__pypackages__` directory and prefers importing packages installed in this location over user or global site-packages. If you are familiar with node, `__pypackages__` works similarly to `node_modules`.
 
@@ -82,6 +82,8 @@ piploc ...
 If PEP 582 is adopted, I think `pip` should default to working in the appropriate `__pypackages__` directory. A flag can be added to install to site-packages, if desired.
 
 ### pipx
+*Note: pipx is included with pythonloc for Python 3.6+ only.*
+
 Installing packages that have so called "entry points" to `__pypackages__` presents a problem. The entry points, or "binaries", are no longer available on your $PATH as they would be if you installed in a virtual environment or to your system. These binaries are massively popular and useful. Examples of binaries are `black`, `pytest`, `tox`, `flake8`, `mypy`, `poetry`, and `pipenv` (and indeed `pythonloc` itself).
 
 `pipx` is a binary installer and runner for Python that, when run, searches for a binary in the appropriate `__pypackages__` location and runs it. If you are familiar with JavaScript's [`npx`](https://www.npmjs.com/package/npx), it's similar to that.
@@ -100,7 +102,7 @@ pipx run --pypackages BINARY [BINARY ARGS]
 ```
 If the binary is not found, and error will be presented.
 
-Something to note here: When installing a new package to an existing `__pypackages__` directory, the entry points will not be created in `.../3.6/lib/bin`, for example, if something is already there. To do that, you need to run `piploc install -U PACKAGE`. When you do that, the entire contents of the directory will be replaced. Fixing this would require a modification to `pip` itself.
+**Note**: When installing a new package to an existing `__pypackages__` directory, the entry points will not be created in `.../3.6/lib/bin`, for example, if something is already there. To do that, you need to run `piploc install -U PACKAGE`. When you do that, the entire contents of the directory will be replaced. Fixing this would require a modification to `pip` itself.
 
 If PEP 582 is adopted, `pipx` will be a good companion tool to run binaries.
 

setup.py

@@ -13,23 +13,21 @@
 import os
 from setuptools import find_packages, setup
 
-DEPENDENCIES = ["pipx>=0.12.2.0"]
-EXCLUDE_FROM_PACKAGES = ["contrib", "docs", "tests*"]
 CURDIR = os.path.abspath(os.path.dirname(__file__))
 
 with io.open(os.path.join(CURDIR, "README.md"), "r", encoding="utf-8") as f:
     README = f.read()
 
 setup(
     name="pythonloc",
-    version="0.1.2.0",
+    version="0.1.2.1",
     author="Chad Smith",
     author_email="[email protected]",
     description="Run Python using packages from local directory __pypackages__",
     long_description=README,
     long_description_content_type="text/markdown",
     url="https://github.com/pipxproject/pythonloc",
-    packages=find_packages(exclude=EXCLUDE_FROM_PACKAGES),
+    packages=find_packages(exclude=["contrib", "docs", "tests*"]),
     include_package_data=True,
     keywords=[],
     scripts=[],
@@ -41,7 +39,7 @@
         ]
     },
     zip_safe=False,
-    install_requires=DEPENDENCIES,
+    install_requires=['pipx>=0.12.2.0;python_version>="3.6"'],
     python_requires=">=2.7",
     # license and classifier list:
     # https://pypi.org/pypi?%3Aaction=list_classifiers
@@ -53,5 +51,6 @@
         "Programming Language :: Python :: 2.7",
         "Programming Language :: Python :: 3.6",
         "Programming Language :: Python :: 3.7",
+        "Programming Language :: Python :: 3.8",
     ],
 )