Mike Orr wrote:
> On Tue, Nov 18, 2008 at 2:02 PM, Matt Wilson <[EMAIL PROTECTED]> wrote:
>> On Nov 18, 12:51 pm, Ian Bicking <[EMAIL PROTECTED]> wrote:
>>> Matt Wilson wrote:
>>>> 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
>>> Hrm... the reason I typically put tests outside of the package is to
>>> skip installing them. Should Pylons just not install that package?
>> What is the downside of installing tests underneath pylons? It might
>> be better to have the tests and not need them instead of the other way
>> around.
>
> The downside of course is disk space. (And on App Engine, the 1000-file
> limit.)
>
> I don't think a best practice has emerged on where to put the tests,
> because some people put them inside the package and others outside.
> My inclination would be to put them inside, because a top-level
> 'tests' is rather presumptive. ("This is the most important package
> in the world, and no other package would have tests.")
Well, with py.test it didn't care about __init__.py, so it wouldn't be a
test at all. But then with Python 2.6 that isn't enough to keep it from
being a package, and nose cared about importability so a lot of them
have __init__.py... which messes it up. But still that tests/ directory
should never be installed if it is top-level.
--
Ian Bicking : [EMAIL PROTECTED] : http://blog.ianbicking.org
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
