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
Because #187 makes it straightforward to run tests without any install, it's problematic that the tests create the astropy configuration directory (~/.astropy by default). This is probably fixable with some clever py.test tricks to fool the tests into using a temporary directory as the configuration directory.
I'm probably mistaken, but I thought this issue came up a little while back, and that you had implemented exactly this--using a temp dir for the tests instead of mucking with ~/.astropy.
I can see why you're thinking that - I had to fix some tests that actually save configuration files - the problem here is that the code actually creates the config/cache directories (but not the files in them) - it's actually in the code that goes and looks for the directories.
Activity
embray commentedon Apr 11, 2012
I'm probably mistaken, but I thought this issue came up a little while back, and that you had implemented exactly this--using a temp dir for the tests instead of mucking with ~/.astropy.
eteq commentedon Apr 12, 2012
I can see why you're thinking that - I had to fix some tests that actually save configuration files - the problem here is that the code actually creates the config/cache directories (but not the files in them) - it's actually in the code that goes and looks for the directories.
embray commentedon Apr 12, 2012
I see what you're saying now.
astrofrog commentedon Jun 16, 2012
Since #283 has been merged, can this be closed?
eteq commentedon Jun 16, 2012
Yep, forgot to use the magic "closes" phrase in one of the commits...
Merge pull request astropy#196 from astrofrog/fix-arm-warnings
Merge pull request astropy#196 from astrofrog/fix-undefined
Merge pull request astropy#196 from taldcroft/maintainers-list