Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

support "setup.py test" and "setup.py develop" #120

Closed
pyflakes-bot opened this issue Jan 8, 2013 · 0 comments
Closed

support "setup.py test" and "setup.py develop" #120

pyflakes-bot opened this issue Jan 8, 2013 · 0 comments

Comments

@pyflakes-bot
Copy link

Original report by florent.x (@florentx?) on Launchpad:


The setup.py could optionally use distribute/setuptools if it is available in the path.

The library distribute (or setuptools) is very common in the Python ecosystem, and many tools depend on them, like "pip install", "virtualenv", "zc.buildout", ...
Of course there's some criticism about these tools, but they exist, they are compatible, and they work fine for a lot of developers.
They fill a use case as explained below.

The benefit of using distribute/setuptools is the additional verbs which are available, like:

$ python setup.py test

This allows to run the tests, and it takes care of installing the 'test_requires' dependencies without other action. Anyone can run the tests without any assumption about the test framework, and without digging through the source code to know which libraries are required (nose, py.test, twisted.trial, unittest, etc...).
This particular use case is not supported by the distutils library.

Another verb which is widely used but not supported by distutils:

$ python setup.py develop

And the best is that it is fully optional.
When the distribute/setuptools package is not installed, it imports 'setup' from distutils and it behaves exactly the same as before.

For the record, there are some users which already suggested this change: kevinw/pyflakes#19

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant