Guido van Rossum wrote: > > > > > What if we add them to CVS and formally maintain them as part of the > > > > core but distribute them as a separate download? > > > > > > Good idea. > > > > All in favour? > > +1, as long as they're not in the CVS subtree that's normally > extracted for a regular source distribution. I propose this location > in the CVS tree: > > python/dist/encodings/... > > (So 'encodings' would be a sibling of 'src', which has been pretty > lonely ever since I started using CVS. ;-) Ok. When Tamito has completed his work on the codecs (he is currently reimplementing them in C), I'll check them in under the new directory. BTW, how should we ship these codecs ? I'd propose to provide a distutils setup.py file which wraps up all codecs under encodings and can be used to create a standard Python add-on "Python-X.X Encoding Add-on". The generated files should then ideally be published right next to the Python source/binary links on the python.org web-pages to achieve high visibility. -- Marc-Andre Lemburg CEO eGenix.com Software GmbH ______________________________________________________________________ Company & Consulting: http://www.egenix.com/ Python Software: http://www.lemburg.com/python/
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