A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2011-July/112679.html below:

[Python-Dev] the history of tests being inside Lib/ in Python

[Python-Dev] the history of tests being inside Lib/ in PythonBenjamin Peterson benjamin at python.org
Sat Jul 30 05:55:51 CEST 2011
2011/7/29 Eli Bendersky <eliben at gmail.com>:
>
> On Sat, Jul 30, 2011 at 06:36, Benjamin Peterson <benjamin at python.org>
> wrote:
>>
>> 2011/7/29 Eli Bendersky <eliben at gmail.com>:
>> > The other thread had some claims (*) that made me wonder - why are the
>> > tests
>> > in Python kept in Lib/ at all?
>> >
>> > AFAIK, this is rather an unusual project structure.
>>
>> Not really. It seems to be about half/half to me.
>
> I guess I'm mis-informed then :) Out of curiosity, could you point to a few
> projects that also place tests inside their code?

Twisted, PyPy, simplejson, Bazaar, buildbot, pyramid, SAGE, Jinja2,
Portage, pylint, and Tahoe-LAFS for starters.



-- 
Regards,
Benjamin
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4