Mailman 3 May 2009 - Python-Dev

special method lookup: how much do we care?
by Benjamin Peterson May 14, 2009

May 14, 2009

A while ago, Guido declared that all special method lookups on new-style classes bypass __getattr__ and __getattribute__. This almost completely consistent now, and I've been working on patching up a few incorrect cases. I've know hit __enter__ and __exit__. The compiler generates LOAD_ATTR instructions for these, so it uses the normal lookup. The only way I can see to fix this is add a new opcode which uses _PyObject_LookupSpecial, but I don't think we really care this much. Opinions? -- Regards, Benjamin

9 18

How to build Python 2.6.2 on HP-UX Itanium with thread support?
by henning.vonbargen＠arcor.de May 13, 2009

May 13, 2009

How to build Python 2.6.2 on HP-UX Itanium with thread support? Note: I know that the first address to post this question is comp.lang.python, but I posted this question a week ago on comp.lang.python (http://groups.google.com/group/comp.lang.python/browse_thread/thread/c7006a…) and unfortunately, I didn't receive any answers. According to Patch 1225212, at least Peter Kropf was able to get Python running with threading support on this platform, though AFAIK he was not using GCC. But I … [View More]

4 4

Shorter release schedule?
by Antoine Pitrou May 13, 2009

May 13, 2009

Hello, Just food for thought here, but seeing how 3.1 is going to be a real featureful schedule despite being released shortly after 3.0, wouldn't it make sense to tighten future release planning a little? I was thinking something like doing a major release every 12 months (rather than 18 to 24 months as has been heuristically the case lately). This could also imply switching to some kind of loosely time-based release system. If I'm wildly off-base, you can either flame me, ignore me, or … [View More]

12 14

Re: [Python-Dev] Shorter release schedule?
by Bugbee, Larry May 13, 2009

May 13, 2009

>From the perspective of this application developer and prototyper... In general, releases should be more frequent when the language is less mature and perhaps lacking. With maturity one seeks stability and less frequency. Python is, for the most part, a mature language. I submit the issue is less a question of frequency, but more a question of the number and value of each of the new features. Too many new features added to a mature language begs the question of simplicity vs … [View More]

1 0

py3k, cgi, email, and form-data
by Robert Brewer May 13, 2009

May 13, 2009

There's a major change in functionality in the cgi module between Python 2 and Python 3 which I've just run across: the behavior of FieldStorage.read_multi, specifically when an HTTP app accepts a file upload within a multipart/form-data payload. In Python 2, each part would be read in sequence within its own FieldStorage instance. This allowed file uploads to be shunted to a TemporaryFile (via make_file) as needed: klass = self.FieldStorageClass or self.__class__ part = klass(self.fp,… [View More]

3 3

CVE-2008-5983 "untrusted python modules search path"
by Antoine Pitrou May 12, 2009

May 12, 2009

Hello, I don't think it has already posted to the list, apologies if it has. Some Linux tools and vendors have been hit by an alleged "security hole" where an embedded Python interpreter will prepend the current working directory to sys.path as soon as PySys_SetArgv() is called by the embedding application. This means, for example, that a Python file in the working directory can break plugins or extensions written for that application if the Python file happens to shadow another module. … [View More]

2 1

Switchover: mail.python.org
by Aahz May 12, 2009

May 12, 2009

On Monday 2009-05-11, mail.python.org will be switched to another machine starting roughly at 14:00 UTC. This should be invisible (expected downtime is less than ten minutes). -- Aahz (aahz(a)pythoncraft.com) <*> http://www.pythoncraft.com/ "It is easier to optimize correct code than to correct optimized code." --Bill Harlan

3 3

using help function in Py3k
by s|s May 12, 2009

May 12, 2009

Hello, I Ran Python 3.0 for the first time. I used help() function and wrote "modules hash". It issues an error. Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/home/ss/eproj/xapian/INST//lib/python3.0/site.py", line 427, in __call__ return pydoc.help(*args, **kwds) File "/home/ss/eproj/xapian/INST//lib/python3.0/pydoc.py", line 1675, in __call__ self.interact() File "/home/ss/eproj/xapian/INST//lib/python3.0/pydoc.py", line 1693, in … [View More]

3 3

albatross backup
by "Martin v. Löwis" May 12, 2009

May 12, 2009

Hi Sean, Can you please setup backup for albatross? I gave sudo permissions to the "jafo" user, which has the key jafo(a)guin.tummy.com authorized. I think the policy now is that root logins to albatross are not allowed. So what might work is this: Create an rsyncbackup user, and give it sudo permission to run rsync (any command line arguments). Put your backup pubkey into rsyncbackup's authorized_keys. Could that actually work? albatross admins: would that be an acceptable setup? As for … [View More]

2 2

py3k, cgi, and form-data
by Robert Brewer May 11, 2009

May 11, 2009

There's a major change in functionality in the cgi module between Python 2 and Python 3 which I've just run across: the behavior of FieldStorage.read_multi, specifically when an HTTP app accepts a file upload within a multipart/form-data payload. In Python 2, each part would be read in sequence within its own FieldStorage instance. This allowed file uploads to be shunted to a TemporaryFile (via make_file) as needed: klass = self.FieldStorageClass or self.__class__ part = klass(self.fp,… [View More]

1 0

Proposed: drop unnecessary "context" pointer from PyGetSetDef
by Larry Hastings May 8, 2009

May 8, 2009

I should have brought this up to python-dev before--sorry for being so slow. It's already in the tracker for a couple of days: http://bugs.python.org/issue5880 The idea: PyGetSetDef has this "void *closure" field that acts like a context pointer. You stick it in the PyGetSetDef, and it gets passed back to you when your getter or setter is called. It's a reasonable API design, but in practice you almost never need it. Meanwhile, it clutters up CPython, particularly typeobject.c; … [View More]

7 14

Easy way to detect filesystem case-sensitivity?
by Brett Cannon May 8, 2009

May 8, 2009

[my python-dev sabbatical is still in effect, so make sure I am at least cc'ed on any replies to this email] I cannot be the only person who has a need to run tests conditionally based on whether the file system is case-sensitive or not, so I feel like I am re-inventing the wheel for issue 5442 to handle OS X with a case-sensitive filesystem. Is there a boolean somewhere that I can simply check or get to know whether the filesystem is case-sensitive? -Brett

7 7

Summary of Python tracker Issues
by Python tracker May 8, 2009

May 8, 2009

ACTIVITY SUMMARY (05/01/09 - 05/08/09) Python tracker at http://bugs.python.org/ To view or respond to any of the issues listed below, click on the issue number. Do NOT respond to this message. 2188 open (+45) / 15604 closed (+30) / 17792 total (+75) Open issues with patches: 848 Average duration of open issues: 646 days. Median duration of open issues: 396 days. Open Issues Breakdown open 2153 (+45) pending 34 ( +0) Issues Created Or Reopened (75) … [View More]

1 0

feature request 5804
by Kristján Valur Jónsson May 8, 2009

May 8, 2009

Hello there. I have sumitted the following patch: Add an 'offset' argument to zlib.decompress http://bugs.python.org/issue5804 I'd be interested on getting some more feedback on it. Kristján

1 0

PEP 383 update: utf8b is now the error handler
by "Martin v. Löwis" May 8, 2009

May 8, 2009

With issue 3672 resolved, it is now unnecessary to introduce an utf-8b codec, since the utf-8 codec will properly report errors for all byte sequences invalid in UTF-8, including lone surrogates. Therefore, utf-8b can be implemented solely through the error handler. Glenn Linderman suggested that the name "python-escape" is not very descriptive, so I've changed the name to "utf8b". I've updated the PEP accordingly. Regards, Martin

18 98

py3k build broken
by Eric Smith May 8, 2009

May 8, 2009

Tarek: With you ARFLAGS change, I now get the following error on a 32 bit Fedora 6 box. I've done "make distclean" and "./configure": $ make ... gcc -pthread -fno-strict-aliasing -g -Wall -Wstrict-prototypes -I. -IInclude -I./Include -DPy_BUILD_CORE -I./Modules/_io -c ./Modules/_io/textio.c -o Modules/textio.o gcc -pthread -fno-strict-aliasing -g -Wall -Wstrict-prototypes -I. -IInclude -I./Include -DPy_BUILD_CORE -I./Modules/_io -c ./Modules/_io/stringio.c -o Modules/stringio.o … [View More]gcc -pthread -fno-strict-aliasing -g -Wall -Wstrict-prototypes -I. -IInclude -I./Include -DPy_BUILD_CORE -c ./Modules/zipimport.c -o Modules/zipimport.o ./Modules/zipimport.c: In function ‘get_module_code’: ./Modules/zipimport.c:1132: warning: format ‘%c’ expects type ‘int’, but argument 3 has type ‘long int’ gcc -pthread -fno-strict-aliasing -g -Wall -Wstrict-prototypes -I. -IInclude -I./Include -DPy_BUILD_CORE -c ./Modules/symtablemodule.c -o Modules/symtablemodule.o gcc -pthread -fno-strict-aliasing -g -Wall -Wstrict-prototypes -I. -IInclude -I./Include -DPy_BUILD_CORE -c ./Modules/xxsubtype.c -o Modules/xxsubtype.o gcc -pthread -c -fno-strict-aliasing -g -Wall -Wstrict-prototypes -I. -IInclude -I./Include -DPy_BUILD_CORE -DSVNVERSION=\"`LC_ALL=C svnversion .`\" -o Modules/getbuildinfo.o ./Modules/getbuildinfo.c rm -f libpython3.1.a ar @ARFLAGS@ libpython3.1.a Modules/getbuildinfo.o ar: illegal option -- @ Usage: ar [emulation options] [-]{dmpqrstx}[abcfilNoPsSuvV] [member-name] [count] archive-file file... ar -M [<mri-script] commands: d - delete file(s) from the archive m[ab] - move file(s) in the archive p - print file(s) found in the archive q[f] - quick append file(s) to the archive r[ab][f][u] - replace existing or insert new file(s) into the archive t - display contents of archive x[o] - extract file(s) from the archive command specific modifiers: [a] - put file(s) after [member-name] [b] - put file(s) before [member-name] (same as [i]) [N] - use instance [count] of name [f] - truncate inserted file names [P] - use full path names when matching [o] - preserve original dates [u] - only replace files that are newer than current archive contents generic modifiers: [c] - do not warn if the library had to be created [s] - create an archive index (cf. ranlib) [S] - do not build a symbol table [v] - be verbose [V] - display the version number @<file> - read options from <file> emulation options: No emulation specific options ar: supported targets: elf32-i386 a.out-i386-linux efi-app-ia32 elf32-little elf32-big srec symbolsrec tekhex binary ihex trad-core make: *** [libpython3.1.a] Error 1 [View Less]

3 5

Adding a "sysconfig" module in the stdlib
by Tarek Ziadé May 8, 2009

May 8, 2009

Hello, I am trying to refactor distutils.log in order to use logging but I have been bugged by the fact that site.py uses distutils.util.get_platform() in "addbuilddir". The problem is the order of imports at initialization time : importing "logging" into distutils will make the initialization/build fail because site.py wil break when trying to import "logging", then "time". Anyways, So why site.py looks into distutils ? because distutils has a few functions to get some info about the … [View More]

3 2

typo in 8.1.3.1. Format Specification Mini-Language?
by Neal Becker May 7, 2009

May 7, 2009

"format_spec ::= [[fill]align][sign][#][0][width][.precision][type]" "The precision is ignored for integer values." In [36]: '%3x' % 10 Out[36]: ' a' In [37]: '%.3x' % 10 Out[37]: '00a' Apparently, precision is _not_ ignored?

3 4

Re: [Python-Dev] Help on issue 5941
by Tarek Ziadé May 7, 2009

May 7, 2009

On Thu, May 7, 2009 at 1:37 PM, David Cournapeau <cournape(a)gmail.com> wrote: > On Thu, May 7, 2009 at 7:07 PM, Tarek Ziadé <ziade.tarek(a)gmail.com> wrote: >> On Thu, May 7, 2009 at 11:50 AM, David Cournapeau <cournape(a)gmail.com> wrote: >>> Then, in the customize_compiler function, set archiver to $AR + >>> $ARFLAGS. IOW, just copying the logic used for e.g. ldshared, >>> >>> I can prepare a patch if you want, >> >> … [View More]

2 2

Help on issue 5941
by Tarek Ziadé May 7, 2009

May 7, 2009

Hello, I need some help on http://bugs.python.org/issue5941 The bug is quite simple: the Distutils unixcompiler used to set the archiver command to "ar -rc". For quite a while now, this behavior has changed in order to be able to customize the compiler behavior from the environment. That introduced a regression because the mechanism in Distutils that looks for the AR variable in the environment also looks into the Makefile of Python. (in the Makefile then is os.environ) And as a matter of … [View More]

2 2

[RELEASED] Python 3.1 beta 1
by Benjamin Peterson May 7, 2009

May 7, 2009

On behalf of the Python development team, I'm thrilled to announce the first and only beta release of Python 3.1. Python 3.1 focuses on the stabilization and optimization of features and changes Python 3.0 introduced. For example, the new I/O system has been rewritten in C for speed. File system APIs that use unicode strings now handle paths with undecodable bytes in them. [1] Other features include an ordered dictionary implementation and support for ttk Tile in Tkinter. For a more … [View More]

1 0

test - please ignore
by Benjamin Peterson May 7, 2009

May 7, 2009

Some of my messages appear not to have gotten through. -- Regards, Benjamin

1 0

Proposed: add support for UNC paths to all functions in ntpath
by Larry Hastings May 6, 2009

May 6, 2009

I've written a patch for Python 3.1 that changes os.path so it handles UNC paths on Windows: http://bugs.python.org/issue5799 In a Windows path string, a UNC path functions *exactly* like a drive letter. This patch means that the Python path split/join functions treats them as if they were. For instance: >>> splitdrive("A:\\FOO\\BAR.TXT") ("A:", "\\FOO\\BAR.TXT") With this patch applied: >>> splitdrive("\\\\HOSTNAME\\SHARE\\FOO\\BAR.TXT") ("\\\\… [View More]HOSTNAME\\SHARE", "\\FOO\\BAR.TXT") This methodology only breaks down in one place: there is no "default directory" for a UNC share point. E.g. you can say >>> os.chdir("c:") or >>> os.chdir("c:foo\\bar") but you can't say >>> os.chdir("\\\\hostname\\share") But this is irrelevant to the patch. Here's what my patch changes: * Modify join, split, splitdrive, and ismount to add explicit support for UNC paths. (The other functions pick up support from these four.) * Simplify isabs and normpath, now that they don't need to be delicate about UNC paths. * Modify existing unit tests and add new ones. * Document the changes to the API. * Deprecate splitunc, with a warning and a documentation remark. This patch adds one subtle change I hadn't expected. If you call split() with a drive letter followed by a trailing slash, it returns the trailing slash as part of the "head" returned. E.g. >>> os.path.split("\\") ("\\", "") >>> os.path.split("A:\\") ("A:\\", "") This is mentioned in the documentation, as follows: Trailing slashes are stripped from head unless it is the root (one or more slashes only). For some reason, when os.path.split was called with a UNC path with only a trailing slash, it stripped the trailing slash: >>> os.path.split("\\\\hostname\\share\\") ("\\\\hostname\\share", "") My patch changes this behavior; you would now see: >>> os.path.split("\\\\hostname\\share\\") ("\\\\hostname\\share\\", "") I think it's an improvement--this is more consistent. Note that this does *not* break the documented requirement that os.path.join(os.path.split(path)) == path; that continues to work fine. In the interests of full disclosure: I submitted a patch providing this exact behavior just over ten years ago. GvR accepted it into Python 1.5.2b2 (marked "*EXPERIMENTAL*") and removed it from 1.5.2c1. You can read GvR's commentary upon removing it; see comments in Misc/HISTORY <http://svn.python.org/view/python/trunk/Misc/HISTORY> dated "Tue Apr 6 19:38:18 1999". If memory serves correctly, the problems cited were only on Cygwin. At the time Cygwin used "ntpath", and it supported "//a/foo" as an alias for "A:\\FOO". You can see how this would cause Cygwin problems. In the intervening decade, two highly relevant things have happened: * Python no longer uses ntpath for os.path on Cygwin. Instead it uses posixpath. * Cygwin removed the "//a/foo" drive letter hack. In fact, I believe it now support UNC paths. Therefore this patch will have no effect on Cygwin users. What do you think? /larry/ [View Less]

6 8

[RELEASED] Python 3.1 beta 1
by Benjamin Peterson May 6, 2009

May 6, 2009

On behalf of the Python development team, I'm thrilled to announce the first and only beta release of Python 3.1. Python 3.1 focuses on the stabilization and optimization of features and changes Python 3.0 introduced. For example, the new I/O system has been rewritten in C for speed. File system APIs that use unicode strings now handle paths with undecodable bytes in them. [1] Other features include an ordered dictionary implementation and support for ttk Tile in Tkinter. For a more … [View More]

1 0

Undocumented change / bug in Python3's PyMapping_Check
by John Millikin May 6, 2009

May 6, 2009

In Python 2, PyMapping_Check will return 0 for list objects. In Python 3, it returns 1. Obviously, this makes it rather difficult to differentiate between mappings and other sized iterables. In addition, it differs from the behavior of the ``collections.Mapping`` ABC -- isinstance([], collections.Mapping) returns False. I believe the new behavior is erroneous, but would like to confirm that before filing a bug. The behavior can be seen from a C extension, or if you're lazy, using ctypes: … [View More]

2 1