pip executable not found
Using custom index url
I tested 0.2.1 on Python 3.6.10 using: /opt/python/3.6.10/bin/pip install upgrade_ensurepip /opt/python/3.6.10/bin/python -m upgrade_ensurepip --pip /opt/python/3.6.10/bin/python -m venv /opt/util/test5 so I think this is solved
work around ensurepip expecting py2.py3 wheel
Added tag 0.2.1 for changeset b483de629031
Using custom index url
Thanks for pointing out the problem with checking for --pip before calling main. I'll fix that but I am not going to import argparse until I have more options/arguments to process than this one. Until https://bugs.python.org/issue40119 is fixed I'll need to rename the downloaded setuptools wheel
Thanks for the update! I had two issues: To run update_enurepip neither the entry-point update_enurepip, nor the main from python -m update_ensurepip get access to the --pip argument you put on the if __name__ == __main__ block of upgrade_ensurepip/upgrade_ensurepip.py. I recomment a built-in tool like argparse for this, and exposing the arguments to both the main and the entrypoint. In addition I had the following issue after having upgraded and running python -m ensurepip: FileNotFoundError: [Errno...
Thanks for the update! I had two issues: To run update_enurepip neither the entry-point update_enurepip, nor the main from python -m update_ensurepip get access to the --pip argument you put on the if name == main block of upgrade_ensurepip/upgrade_ensurepip.py. I recomment a built-in tool like argparse for this, and exposing the arguments to both the main and the entrypoint. In addition I had the following issue after having upgraded and running python -m ensurepip: FileNotFoundError: [Errno 2]...
Using custom index url
Thanks for the report, I looked at this, but decided not to go with the legacy interface (and a possible dependency on pypi-simple). Instead I added a --pip option that switches from using the JSON info to essentially doing: pip search pip | grep -E '^pip (' to retrieve the version number and when appropriate pip download --dest /your/pythons/wheel/dir --only-binary=:all: pip to download. I hope that gives enough flexibility to the packages and their info from a local (devpi?) repository. If it indeed...
Python 3.8 compatibility
This should be solved now. If you have an opportunity to confirm this, please close this issue.
Thanks for the report, I looked at this, but decided not to go with the legacy interface (and a possible dependency on pypi-simple). Instead I added a --pip option that switches from using the JSON info to essentially doing: pip search pip | grep -E '^pip (' to retrieve the version number and when appropriate pip download --dest /your/pythons/wheel/dir --only-binary=:all: pip to download. I hope that gives enough flexibility to the packages and their info from a local (devpi?) repository.
added option to use pip for search/upgrade
Added tag 0.2.0 for changeset 2da96a577609
re-added
trying to make .rst newest by first removing
test
re-added
trying to get SF to use correct README
oitnb svg taken from oitnb
README.rst updated
typo
Incidentally, it would also be great to make use of the simple index definition, rather than the json based pypi index definition. The former is refered to as the "legacy" interface: https://warehouse.readthedocs.io/api-reference/legacy/, but appears to be better covered by PEPs than the new JSON one. There is a client that you could benefit from at: https://pypi.org/project/pypi-simple/
Using custom index url
update ryd svg
Added tag 0.1.4 for changeset 9ca45da48653
update setup.py for 3.8
Added tag 0.1.3 for changeset 179d8175a38c
initial version
added some documentation
Added tag 0.1.1 for changeset d66152c37743
added __main__.py
remove backup file
version in pypi badge
regenerate .rst
new version badge