Repository navigation
Failures in tests with Python 3.2 - #50
Conversation
|
The |
|
The constants test now passes correctly, and only the WCS test is failing now. |
|
@astrofrog: for the WCS test, you somehow have an extra warning. I'd like to see what it is. In astropy/wcs/tests/test_wcs.py:test_fixes, can you add under |
|
@astrofrog: I think I know why the constants thing happened - if you take a look at http://packages.python.org/distribute/python3.html, it appears we are supposed to have |
|
Ah, good catch. Feel free to add it to master! |
|
@mdboom - the warnings are: By the way, how does one get output to print during tests? I had to write the warnings to a file to be able to view them. |
|
@astrofrog: In my experience, whatever is written to stdout/stderr gets displayed right after the traceback with each failing test. Of course, I realised I asked you to put the print statement after the failing assert, so obviously that line never got run. In any case, see attached fix. |
|
It looks like all tests now pass in Python 2.6, 2.7, 3.1 and 3.2. Merging! |
Failures in tests with Python 3.2
|
Hmm, actually now that I've merged in the changes I'm getting another error in Python 3.1 and 3.2 which I wasn't getting with @mdboom's branch: Is this to do with the addition of the 2to3 option? |
|
Ah, I see it now, too. Yes, indeed it seems 2to3 broke it, but it's a simple fix. Try this commit. |
|
Seems to work, thanks! Merging. |
Failures in tests with Python 3.2
|
All tests now pass in master with 2.6, 2.7, 3.1, and 3.2 on MacOS 10.6.8. |
Failures in tests with Python 3.2
Failures in tests with Python 3.2
…-ourselves Do Sphinx version check ourselves
As of 7946471, two tests have issues with Python 3.2:
@eteq and @mdboom, these relate to code you wrote in constants/init.py and wcs/tests respectively.