search

takluyver / entrypoints

Discover and load entry points from installed packages
https://entrypoints.readthedocs.io/
MIT License
74 stars 29 forks source link

Add `setup.py`? #1

Closed aldanor closed 8 years ago

aldanor commented 8 years ago

@takluyver

Since this package is now a dependency of nbconvert, would you mind adding conventional setupools installer (setup.py)? Even though it's a trivial package, some tools expect setup.py to exist (e.g. conda-build, tox and many others).

This is just a suggestion and would be up to you of course :)

Edit: I understand you're using your own pypi uploader/wrapper, this is a different question though.

takluyver commented 8 years ago

Sorry, but it defeats the point of using flit if I also include and maintain a setup.py file. Any tools using pip should be able to install it from PyPI with no problems. I have an experimental tool flonda which can generate conda packages from flit metadata.

aldanor commented 8 years ago

On a second note, would you please also publish the sdist to PyPI as well? Again, wheel is understandably a better/newer way to distributite, but sdist is still often required mostly to conform with what many build tools expect (e.g. automated conda package builders).

takluyver commented 8 years ago

There is work underway to define new sdist formats:

https://github.com/pypa/interoperability-peps/blob/master/pep-0516-build-system-abstraction.rst https://github.com/pypa/interoperability-peps/blob/master/pep-0517-build-system-abstraction.rst

aldanor commented 8 years ago

@takluyver Yea, I've seen those. And while I wholeheartedly support that I think the existing packages on PyPI should stay accessible by today's tools (accessible to machines, i.e. existing build systems, not just humans).