Build wheels for public releases

[python]

Build wheels for public releases

[msullivan]

I've uploaded a 0.4.2 wheel and released a 0.4.3 with a wheel. (0.4.3 was basically just to catch an update to the URL).

I've updated our internal playbook with directions for creating the wheel

Thanks!

[ilevkivskyi]

Thanks for report! I don't have access to Windows right now. Maybe @ethanhs can give some advice here?

[Drache91]

Well, I cloned mypy_extensions and tried executing the command from the error
message that produces the error (python setup.py egg_info) whilst within the
venv and got the following result:

(venv) PS F:\Programmierung\YTThingy\mypy_extensions> python setup.py egg_info
Traceback (most recent call last):
  File "setup.py", line 3, in <module>
    from setuptools import setup
ModuleNotFoundError: No module named 'setuptools'

When executed with -m it works fine.

(venv) PS F:\Programmierung\YTThingy\mypy_extensions> python -m setup egg_info
F:\Programmierung\YTThingy\venv\lib\site-packages\setuptools\dist.py:475: UserWarning: Normalizing '0.5.0-dev' to '0.5.0.dev0'
  normalized_version,
running egg_info
creating mypy_extensions.egg-info
writing mypy_extensions.egg-info\PKG-INFO
writing dependency_links to mypy_extensions.egg-info\dependency_links.txt
writing requirements to mypy_extensions.egg-info\requires.txt
writing top-level names to mypy_extensions.egg-info\top_level.txt
writing manifest file 'mypy_extensions.egg-info\SOURCES.txt'
reading manifest file 'mypy_extensions.egg-info\SOURCES.txt'
reading manifest template 'MANIFEST.in'

If that is of any help.

[ethanhs]

Unfortunately, I am unable to repro this. Since the project just calls into setuptools, I think you'll have more luck reporting the issue there. If I had to guess it would be something like pip is duplicating the file descriptors for the setup process stdin/stdout, which is failing (there have been various bugs reported about this, but none match your system or Python as far as I can tell).

Btw, as an action item for us, we should probably release wheels so people don't need to run setup.py egg_info as part of install.

[Drache91]

Oh well, thank you non the less :)

I suppose this can be considered closed now?

[ilevkivskyi]

Let's keep this open as a reminder to build wheels for the next release.

[nicktimko]

I'm not sure how this was even possible; I thought PyPI blocked uploads of releases after you uploaded the source distribution for that version/package. Or maybe it was after you upload the binary release?...

In any event, please don't retro-release again, it causes some pain (#15)

[gvanrossum]

Why is this our fault and not a bug in pipenv? Please open an issue with pipenv.