Mailman 3 September 2010 - Python-Dev

Python 2.7 Won't Build
by Tom Browder Sept. 20, 2010

Sept. 20, 2010

I am trying to rebujild the 2.7 maintenance branch and get this error on Ubuntu 10.04.1 LTS: XXX lineno: 743, opcode: 0 Traceback (most recent call last): File "/usr/local/src/python-2.7-maint-svn/Lib/site.py", line 62, in <module> import os File "/usr/local/src/python-2.7-maint-svn/Lib/os.py", line 743, in <module> def urandom(n): SystemError: unknown opcode I installed it successfully once so I may be getting conflicts, but I can't figure out why. There were some … [View More]

7 18

Rework nntlib?
by Antoine Pitrou Sept. 20, 2010

Sept. 20, 2010

Hello, Like the email package, nntplib in py3k is broken (because of various bytes/str mismatches; I suppose the lack of a test suite didn't help when porting). I would like to take the opportunity to improve the API a bit; no heavy re-architecting, but simply a bunch of changes to make it higher-level. Is it acceptable? (and, yes, I would add a test suite) Regards Antoine.

30 121

Some news from my sandbox project
by Victor Stinner Sept. 19, 2010

Sept. 19, 2010

Hi, I'm still developing irregulary my sandbox project since last june. pysandbox is a sandbox to execute untrusted Python code. It is able to execute unmodified Python code with a low overhead. I consider it as stable and secure. http://github.com/haypo/pysandbox/ Today, the biggest problem is the creation of a read only view of the __builtins__ dictionary. I tried to create my own object with the dict API, but I got quickly a segfault. I realized that ceval.c is hardcoded to use PyDict … [View More]

4 9

Re: [Python-Dev] [Catalog-sig] egg_info in PyPI
by Tarek Ziadé Sept. 19, 2010

Sept. 19, 2010

On Fri, Sep 17, 2010 at 10:02 PM, Jannis Leidel <jannis(a)leidel.info> wrote: > On 17.09.2010, at 20:43, Martin v. Löwis wrote: > >> Here at the DZUG conference, we are planning to integrate explicit access to setuptools metadata to the package index. >> >> The current idea is to store the contents of the egg_info directory, >> giving remote access to specific files. By default, PyPI will extract, >> per release, data from the egg that may get uploaded (… [View More]using the first >> one if multiple eggs get uploaded). If no egg gets uploaded, a VM >> based build service will generate it from a source distributions. >> Tools like setuptools or distribute could also directly upload this >> information, e.g. as part of the register command. >> >> Any opinions? > > I'm confused, wouldn't that basically be a slap in the face for the people having worked on PEP345 and distutils2, especially during the Summer of Code? > > Also, and I understand enthusiasm tends to build up during conferences, but wouldn't supporting setuptools' egg-info directory again be a step backwards after all those months of discussion about the direction of Python packaging? Yeah, we worked on a new standard that was accepted - PEP 345 PyPI is currently publishing pep 345 info as a matter of fact - I did the patch and there's one package that already uses it http://pypi.python.org/pypi/Distutils2. (no deps on this one, but other stuff like links..) I am about to release the work we did during GSOC in distutils2, a first beta that includes all the work we done. Now you want to publish another metadata format at PyPI ? If PyPI takes that direction and adopts, promotes and publishes a standard that is not the one we worked on in the past year, this will increase our difficulty to push the new format so its adopted by the tools then the community. People will just get confused because they will find two competing metadata formats That's exactly the situation where we were at, and that's exactly where I don't want to go back. I am not even understanding what's the benefit of doing this since an egg_info directory is obtained at *build* time and can differ from a machine to another, so it seems pretty useless for me to publish this. The whole point of PEP 345 is to extend our metadata to statically provide dependencies at PyPI, thanks to a micro-language that allows you to describe dependencies for any platform. We worked hard to build some standards, but if PyPI doesn't help us here, everything we did and are doing is useless. Tarek -- Tarek Ziadé | http://ziade.org [View Less]

12 30

Re: [Python-Dev] Polymorphic best practices
by John Nagle Sept. 18, 2010

Sept. 18, 2010

On 9/18/2010 2:29 AM, python-dev-request(a)python.org wrote: > Polymorphic best practices [was: (Not) delaying the 3.2 release] If you're hung up on this, try writing the user-level documentation first. Your target audience is a working-level Web programmer, not someone who knows six programming languages and has a CS degree. If the explanation is too complex, so is the design. Coding in this area is quite hard to do right. There are issues with character set, HTML encoding, URL … [View More]

1 0

Re: [Python-Dev] [Python-checkins] r84877 - python/branches/release27-maint/Lib/posixpath.py
by Victor Stinner Sept. 18, 2010

Sept. 18, 2010

Le samedi 18 septembre 2010 07:40:44, hirokazu.yamamoto a écrit : > Author: hirokazu.yamamoto > Date: Sat Sep 18 07:40:44 2010 > New Revision: 84877 > > Log: > Added missing import. > > Modified: python/branches/release27-maint/Lib/posixpath.py > =========================================================================== > === --- python/branches/release27-maint/Lib/posixpath.py (original) > +++ python/branches/release27-maint/Lib/posixpath.py Sat Sep 18 07:40:… [View More]

1 0

Summary of Python tracker Issues
by Python tracker Sept. 17, 2010

Sept. 17, 2010

ACTIVITY SUMMARY (2010-09-10 - 2010-09-17) Python tracker at http://bugs.python.org/ To view or respond to any of the issues listed below, click on the issue. Do NOT respond to this message. Issues stats: open 2541 (+42) closed 19128 (+69) total 21669 (+65) Open issues with patches: 1060 Issues opened (42) ================== #9824: SimpleCookie should escape commas and semi-colons http://bugs.python.org/issue9824 opened by spookylukey #9831: test_distutils fails on MacOSX 10.… [View More]

1 0

Re: [Python-Dev] Add PEP 444, Python Web3 Interface.
by John Nagle Sept. 17, 2010

Sept. 17, 2010

On 9/15/2010 4:44 PM, python-dev-request(a)python.org wrote: > ``SERVER_PORT`` must be a bytes instance (not an integer). What's that supposed to mean? What goes in the "bytes instance"? A character string in some format? A long binary number? If the latter, with which byte ordering? What problem does this\ solve? John Nagle

2 1

Re: [Python-Dev] 3.x as the official release
by Éric Araujo Sept. 16, 2010

Sept. 16, 2010

> If you're talking about distutils2 on Python 3, then of course > anything goes: backward compatibility isn't an issue. For 2.x, not > writing the files would indeed produce backward compatibility problems. I was talking about distutils in 3.2 (or in the release where wsgiref.egg-info goes away). install_egg_info.py has already been turned into install_distinfo.py in distutils2, following PEP 376. Thank you for your reply, I withdraw my suggestion. Regards

1 0

Re: [Python-Dev] 3.x as the official release
by P.J. Eby Sept. 16, 2010

Sept. 16, 2010

At 10:18 PM 9/16/2010 +0200, Ãric Araujo wrote: >Le 15/09/2010 21:45, Tarek ZiadÃ© a Ã©crit : > Could we remove in >any case the wsgiref.egg-info file ? Since we've > been working on a >new format for that (PEP 376), that should be > starting to get used >in the coming years, it'll be a bit of a > non-sense to have that >metadata file in the sdtlib shipped with 3,2 On a related subject: >Would it make sense not to run install_egg_info from install >… [View More]

1 0