Mailman 3 January 2012 - Python-Dev

Re: [Python-Dev] A new dictionary implementation
by Mark Shannon Jan. 29, 2012

Jan. 29, 2012

Matt Joiner wrote: > Mark, Good luck with getting this in, I'm also hopeful about coroutines, > maybe after pushing your dict optimization your coroutine implementation > will get more consideration. Shush, don't say the C word or you'll put people off ;) I'm actually not that fussed about the coroutine implementation. With "yield from" generators have all the power of asymmetric coroutines. I think my coroutine implementation is a neater way to do things, but it is not worth the … [View More]

1 0

Re: [Python-Dev] [issue13703] Hash collision security issue
by Glenn Linderman Jan. 29, 2012

Jan. 29, 2012

On 1/26/2012 10:25 PM, Gregory P. Smith wrote: > (and on top of all of this I believe we're all settled on having per > interpreter hash randomization_as well_ in 3.3; but this AVL tree > approach is one nice option for a backport to fix the major > vulnerability) If the tree code cures the problem, then randomization just makes debugging harder. I think if it is included in 3.3, it needs to have a switch to turn it on/off (whichever is not default). I'm curious why AVL tree … [View More]

5 11

#include "Python.h"
by Andrea Crotti Jan. 29, 2012

Jan. 29, 2012

I have a newbie question about CPython. Looking at the C code I noted that for example in tupleobject.c there is only one include #include "Python.h" Python.h actually includes everything as far as I can I see so: - it's very hard with a not-enough smart editor to find out where the not-locally defined symbols are actually defined (well sure that is not a problem for most of the people) - if all the files include python.h, doesn't it generate very big object files? Or is it not a … [View More]

5 6

Hashing proposal: 64-bit hash
by Serhiy Storchaka Jan. 28, 2012

Jan. 28, 2012

As already mentioned, the vulnerability of 64-bit Python rather theoretical and not practical. The size of the hash makes the attack is extremely unlikely. Perhaps the easiest change, avoid 32-bit Python on the vulnerability, will use 64-bit (or more) hash on all platforms. The performance is comparable to the randomization. Keys order depended code will be braked not stronger than when you change the platform or Python feature version. Maybe all the 64 bits used only for strings, and for other … [View More]

4 6

Python 3 benchmarks
by Maciej Fijalkowski Jan. 28, 2012

Jan. 28, 2012

Hi Something that's maybe worth mentioning is that the "official" python benchmark suite http://hg.python.org/benchmarks/ has a pretty incomplete set of benchmarks for python 3 compared to say what we run for pypy: https://bitbucket.org/pypy/benchmarks I think a very worthwhile project would be to try to port other benchmarks (that actually use existing python projects like sympy or django) for those that has been ported to python 3. Any thoughts? Cheers, fijal

2 1

Summary of Python tracker Issues
by Python tracker Jan. 27, 2012

Jan. 27, 2012

ACTIVITY SUMMARY (2012-01-20 - 2012-01-27) 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 counts and deltas: open 3234 (+25) closed 22437 (+32) total 25671 (+57) Open issues with patches: 1391 Issues opened (44) ================== #6631: Disallow relative files paths in urllib*.open() http://bugs.python.org/issue6631 reopened by amaury.forgeotdarc #13829: exception … [View More]

1 0

Re: [Python-Dev] [Python-ideas] Coroutines and PEP 380
by Mark Shannon Jan. 26, 2012

Jan. 26, 2012

Nick Coghlan wrote: > (redirecting to python-ideas - coroutine proposals are nowhere near > mature enough for python-dev) > > On Wed, Jan 25, 2012 at 5:35 PM, Matt Joiner <anacrolix(a)gmail.com> wrote: >> If someone can explain what's stopping real coroutines being into >> Python (3.3), that would be great. > > The general issues with that kind of idea: > - the author hasn't offered the code for inclusion and relicensing > under the PSF license (thus … [View More]

1 0

Packaging and setuptools compatibility
by Alexis Métaireau Jan. 25, 2012

Jan. 25, 2012

Hi folks, I have this in my mind since a long time, but I didn't talked about that on this list, was only writing on distutils@ or another list we had for distutils2 (the fellowship of packaging). AFAIK, we're almost good about packaging in python 3.3, but there is still something that keeps bogging me. What we've done (I worked especially on this bit) is to provide a compatibility layer for the distributions packaged using setuptools/distribute. What it does, basically, is to install … [View More]

3 2

Status of Mac buildbots
by Nadeem Vawda Jan. 25, 2012

Jan. 25, 2012

Hi all, I've noticed that most of the Mac buildbots have been offline for a while: * http://www.python.org/dev/buildbot/all/buildslaves/parc-snowleopard-1 * http://www.python.org/dev/buildbot/all/buildslaves/parc-tiger-1 * http://www.python.org/dev/buildbot/all/buildslaves/parc-leopard-1 Does anyone know what the status of these bots is? Are they permanently down, or just temporarily inaccessible? Cheers, Nadeem

2 2

PEP 380 ("yield from") is now Final
by Nick Coghlan Jan. 25, 2012

Jan. 25, 2012

I marked PEP 380 as Final this evening, after pushing the tested and documented implementation to hg.python.org: http://hg.python.org/cpython/rev/d64ac9ab4cd0 As the list of names in the NEWS and What's New entries suggests, it was quite a collaborative effort to get this one over the line, and that's without even listing all the people that offered helpful suggestions and comments along the way :) print("\n".join(list((lambda:(yield from ("Cheers,", "Nick")))()))) -- Nick Coghlan &… [View More]

11 19