You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
pex does not work well with a local pypi. So I followed the work around described here #270 . However, if you have dependencies with a dash in the name like javaobj-py3 or asn1-modules, pex fails. The following demonstrates the issue.
Note in the following example, pip is configured to use a local pypi like so:
seems to me like the filename of the wheel as stored in your local pypi server is malformed, so it would make sense that pex would fail to resolve. the use of - in the package name in a filename is disallowed by the wheel spec. how are you generating it?
noting that the filename on pypi is: javaobj_py3-0.2.3-py2.py3-none-any.whl, which is correct and would 'just work' in this case.
going to tentatively mark this one as 'WONTFIX' - despite pip's accommodation of broken wheel filenames, we likely won't want to bother supporting this in pex since the correct path to proper wheel naming is straightforward and nets the added benefit of future proofing.
could be persuaded otherwise if there was a concrete case for it.
pex does not work well with a local pypi. So I followed the work around described here #270 . However, if you have dependencies with a dash in the name like javaobj-py3 or asn1-modules, pex fails. The following demonstrates the issue.
Note in the following example, pip is configured to use a local pypi like so:
First download the wheel:
Now try creating a pex file with it.
Here is a workaround which will create a hard link to all python modules and replace the a dash with underscore.
The text was updated successfully, but these errors were encountered: