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
$ python setup.py test --nocapture --nose-verbose --processes=5 --process-timeout=300
...
running test
Traceback (most recent call last):
File "setup.py", line 381, in <module>
**extra_args
File "/usr/lib/python3.5/distutils/core.py", line 148, in setup
dist.run_commands()
File "/usr/lib/python3.5/distutils/dist.py", line 955, in run_commands
self.run_command(cmd)
File "/usr/lib/python3.5/distutils/dist.py", line 973, in run_command
cmd_obj.ensure_finalized()
File "/usr/lib/python3.5/distutils/cmd.py", line 107, in ensure_finalized
self.finalize_options()
File "setup.py", line 158, in finalize_options
self.test_args = []
AttributeError: can't set attribute
Yes but we are not using it. It's breaks Travis and we have to maintain the 2 other ways of testing which does not install the test only dependencies but raises a warning if they are missing. I would much rather make go for the simple solution and just raise if nose or mock is missing that seems way more reliable to me.
FWIW: I wasn't advocating any particular solution here, just to revisit all the options we've ended up with and see how we can simplify. I know it was painful to get the test command in.
Activity
jenshnielsen commentedon Oct 26, 2015
Thanks. I think they still run with the old
python tests.pyI am starting to think that we should get rid of the setup.py test entry point?tacaswell commentedon Oct 26, 2015
The reason that we have the
setup.py testentry point at all is so that we can have test-only requirements.jenshnielsen commentedon Oct 26, 2015
Yes but we are not using it. It's breaks Travis and we have to maintain the 2 other ways of testing which does not install the test only dependencies but raises a warning if they are missing. I would much rather make go for the simple solution and just raise if nose or mock is missing that seems way more reliable to me.
mdboom commentedon Oct 26, 2015
I would love to make our test running more "sane" -- or at the least have fewer options. Maybe a good discussion topic for today's hangout?
tacaswell commentedon Oct 26, 2015
fair enough. Ripping it back out is fine by me, it was just painful to put in.
mdboom commentedon Oct 26, 2015
FWIW: I wasn't advocating any particular solution here, just to revisit all the options we've ended up with and see how we can simplify. I know it was painful to get the
testcommand in.anntzer commentedon Jun 21, 2017
setup.py test is no longer a documented test entry point, so closing.