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-January/107708.html below:

[Python-Dev] Why do we bundle lib2to3 with Python? Was: Location of tests for packages

[Python-Dev] Why do we bundle lib2to3 with Python? Was: Location of tests for packages [Python-Dev] Why do we bundle lib2to3 with Python? Was: Location of tests for packagesBrett Cannon brett at python.org
Thu Jan 27 18:22:47 CET 2011 
2011/1/27 Łukasz Langa <lukasz at langa.pl>:
>
> W dniu 2011-01-24 23:13, Benjamin Peterson pisze:
>>
>>  I prefer lib2to3 tests to stay in lib2to3/.
>
> On a related note, I had trouble myself with using outdated 2to3 and
> heard complaints about that at least a couple of times. What do we gain
> from bundling 2to3 with Python?

Same thing we get when we bundle anything with Python: one less
dependency for people to download. Obviously this shouldn't be as much
of an issue once Python 3.2 is out.
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