After easy_installing Pylons, my site-packages folder has an easy- install.pth file that points to my Pylons-0.9.7....egg folder.
Inside that egg folder, I've got these directories: $ ls ~/virtualenvs/scratch/lib/python2.5/site-packages/Pylons-0.9.7rc3- py2.5.egg/ EGG-INFO pylons tests See that tests directory? As far as I can tell, the combination of the lines in easy-install.pth and that tests directory mean that whenever I run import tests, I get this particular tests module, rather than the tests folder in the current directory. This is problematic for me because it is masking other tests modules that also want to hog the top level. TurboGears holds its tests directory inside its turbogears package. Should Pylons do something similar? I'm suggesting that somebody with svn commit powers does: $ svn mv tests pylons/ And then hopefully this problem would go away. Maybe a completely different solution could be to not even install the tests into site-packages. Thoughts? Matt --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
