I suggesting to make in-place builds the required way to build pygr for testing.
python setup.py build_ext -i This allows us to test modified pure python modules without having to rerun the build command. There is some nice work done to add the platform specific build directory to the import path, unfortunately it seems that in the end the two approaches cannot be reconciled. We cannot have both a build directory while maintaining priority for the source directory because once python finds the pygr in the source directory (which it always will) the rest of the modules of the package will be imported relative that path. The only reason that this works for those who use the current approach is that they do not run the both commands (build and build_ext). As soon as you run both commands you've now run into the problem of either importing from the wrong location or not being able to import modified modules without a rebuild (and both can be devious). I am sure that there are some workarounds but from simplicity point of view let's just mandate the inplace builds for testing, and by default the framework will check for this. I have implemented a --nopathfix flag that you can pass to any test module to indicate that you don't want it to alter the import paths (to test global installations). --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pygr-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/pygr-dev?hl=en -~----------~----~----~----~------~----~------~--~---
