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
python setup.py develop #92
Comments
We don't (yet) use setuptools for our setup.py file. The python standard distutils don't support the 'develop' option. But I was thinking about if we should not start to use setuptools or distribute. |
@filipefigcorreia: You can make this work locally, if you like. In setup.py replace the line
with
That's all you need. |
@trbs I see. I managed to miss that this command is supposed to be available on setuptools but not on distutils... @MichaelBlume thanks. it works! |
@filipefigcorreia: no problem =) distutils is part of Python, so everyone's assumed to have it. setuptools is an optional install (though a pretty popular one) and gives some extra options. So it's up to each project whether to require that its users install the optional package and thus get those options. I think a good balance might be struck by try: from setuptools import setup except ImportError: from distutils.core import setup |
Cool |
torch.utils.ffi is deprecated. Please use cpp extensions instead. |
|
Think these comments are not related to |
Shouldn't this work for django-extensions?
python setup.py develop
It works in other projects, but when I run it with django-extensions I get the strangest error message:
$ python setup.py develop
usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
or: setup.py --help [cmd1 cmd2 ...]
or: setup.py --help-commands
or: setup.py cmd --help
I've also looked at the contents of setup.py, and haven't spotted anything unusual.
The text was updated successfully, but these errors were encountered: