[Python-Dev] Request for developer privileges.
Hello, my name is Lars Gustäbel (SF gustaebel). I contributed tarfile.py to the Python standard library in January 2003 and have been the maintainer since then. I have provided about 25 patches over the years, most of them fixes, some of them new features and improvements. As a result, I am pretty familiar with the Python development process. If possible I would like to get developer privileges to be able to work more actively on tarfile.py for a certain time. I am currently implementing read-write POSIX.1-2001 pax format support. Development is still in progress, but it is already clear at this point, that it will be a complex change, which will definitely require some maintenance once it is finished and in day-to-day use. I would like to clean up the tarfile test suite during this process as well. The introduction of the pax format is important because it is the first tar specification that puts an end to those annoying limitations of the "original" tar format. It will become the default format for GNU tar some day. Thank you, Lars. -- Lars Gustäbel [EMAIL PROTECTED] ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] New Python-Ideas mailing list
At Guido's suggestion, a new mailing list has been created named Python-Ideas (http://mail.python.org/mailman/listinfo/python-ideas). This list is meant as a place for speculative, pie-in-the-sky language design ideas to be discussed and honed to the point of practically being a PEP before being presented to python-dev or python-3000. This allows both python-dev and python-3000 to focus more on implementation work or final approval/denial of ideas instead of being flooded with long threads where people discuss ideas that are too nebulous to be considered for inclusion into Python. Like python-dev and python-3000, Python-Ideas requires you subscribe before you can post, but there is no moderator approval required. If you are interested in helping me out by being an administrator or moderator for the list, please let me know. -Brett ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] Listing of PEP 328 status and possible minor oversight
I just noticed that PEP 328 (relative imports) is listed as an accepted PEP, but not completed. Is this because there is still things to do for 2.6 and 2.7? Or did someone just forget to move it to the completed PEPs section of the PEP index? If it is the former then PEP 362 will need to be moved. I also noticed that there is no mention of removing import redirection to a top-level module by having None in sys.modules. Was this for backwards-compatibility issues, or was it just not thought of? -Brett ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Listing of PEP 328 status and possible minor oversight
On 12/20/06, Brett Cannon <[EMAIL PROTECTED]> wrote: I just noticed that PEP 328 (relative imports) is listed as an accepted PEP, but not completed. Is this because there is still things to do for 2.6 and 2.7? Or did someone just forget to move it to the completed PEPs section of the PEP index? If it is the former then PEP 362 will need to be moved. There was some minor finagling about the wording of the PEP, I think, that I was still supposed to do. Some explanation of common practices, maybe; the python-dev archives might have it. I could never get it into the PEP the right way, the end result was never that big a change (and a bit awkward with the rest.) I also noticed that there is no mention of removing import redirection to a top-level module by having None in sys.modules. Was this for backwards-compatibility issues, or was it just not thought of? I don't think I've ever heard of that idea. I don't know what 'import redirection' is either. But maybe it was one of those things that were still supposed to go into PEP 328. -- Thomas Wouters <[EMAIL PROTECTED]> Hi! I'm a .signature virus! copy me into your .signature file to help me spread! ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Listing of PEP 328 status and possible minor oversight
On 12/20/06, Thomas Wouters <[EMAIL PROTECTED]> wrote: On 12/20/06, Brett Cannon <[EMAIL PROTECTED]> wrote: > > I just noticed that PEP 328 (relative imports) is listed as an accepted > PEP, but not completed. Is this because there is still things to do for > 2.6 and 2.7? Or did someone just forget to move it to the completed > PEPs section of the PEP index? If it is the former then PEP 362 will need > to be moved. There was some minor finagling about the wording of the PEP, I think, that I was still supposed to do. Some explanation of common practices, maybe; the python-dev archives might have it. I could never get it into the PEP the right way, the end result was never that big a change (and a bit awkward with the rest.) I also noticed that there is no mention of removing import redirection to > a top-level module by having None in sys.modules. Was this for > backwards-compatibility issues, or was it just not thought of? I don't think I've ever heard of that idea. I don't know what 'import redirection' is either. But maybe it was one of those things that were still supposed to go into PEP 328. So if sys.modules has an entry of None for a dotted name then import is supposed to stop trying to import that name and instead import a top-level name. This happens if you do ``import string`` from within a package and there is no 'string' module there. This leads to sys.modules['pkg.string'] being None and thus redirecting to sys.modules['string']. This is only useful for classic relative import semantics and thus can probably go once absolute imports are the only way to do imports. -Brett ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Request for developer privileges.
Hi Lars. Thanks for all your work on tarfile! Please send your ssh2 key to pydotorg at python.org as an attachment. One of us will add your key. Hopefully I can remember how to do it. Here's some other info: http://www.python.org/dev/faq/#subversion-svn I can't add you to SF to be assigned bugs since I'm not an admin. So hopefully one of the admins can either add me as an admin or you as a developer. I already updated Misc/developers.txt. n -- On 12/20/06, Lars Gustäbel <[EMAIL PROTECTED]> wrote: > Hello, > > my name is Lars Gustäbel (SF gustaebel). I contributed > tarfile.py to the Python standard library in January 2003 and > have been the maintainer since then. I have provided about 25 > patches over the years, most of them fixes, some of them new > features and improvements. As a result, I am pretty familiar > with the Python development process. > > If possible I would like to get developer privileges to be able > to work more actively on tarfile.py for a certain time. > > I am currently implementing read-write POSIX.1-2001 pax format > support. Development is still in progress, but it is already > clear at this point, that it will be a complex change, which > will definitely require some maintenance once it is finished and > in day-to-day use. I would like to clean up the tarfile test > suite during this process as well. The introduction of the pax > format is important because it is the first tar specification > that puts an end to those annoying limitations of the "original" > tar format. It will become the default format for GNU tar some > day. > > Thank you, > Lars. > > -- > Lars Gustäbel > [EMAIL PROTECTED] > ___ > Python-Dev mailing list > [email protected] > http://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > http://mail.python.org/mailman/options/python-dev/nnorwitz%40gmail.com > ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
