Re: [Python-Dev] [RELEASE] Python 2.7.4 release candidate 1

Am 26.03.2013 um 23:05 schrieb Sean Felipe Wolfe : >> Anyway, you should trust Brett Canon: "Python 3.3: Trust Me, It's >> Better Than Python 2.7". >> >> https://speakerdeck.com/pyconslides/python-3-dot-3-trust-me-its-better-than-python-2-dot-7-by-dr-brett-cannon > Was there supposed to be audio

Re: [Python-Dev] Hash collision security issue (now public)

Hi, how about Option d: Host based salt + Easy-ish to implement – how about basing it on the hostname for example? + transparent for all processes on the same host - probably unit test breakage In fact, we could use host based as default with the option to specify own which would solve the

Re: [Python-Dev] [Python-checkins] cpython: Issue #9993: When the source and destination are on different filesystems,

> > Issue #9993: When the source and destination are on different filesystems, > > and the source is a symlink, shutil.move() now recreates a symlink on the > > destination instead of copying the file contents. > > Patch by Jonathan Niehof and Hynek Schlawack. > > That

Re: [Python-Dev] Status of the fix for the hash collision ulnerability

Am Sonntag, 15. Januar 2012 um 05:49 schrieb Steven D'Aprano: > > I don't think anyone doubts that this will break lots of code (at least, > > the arguments I've heard have been "their code is broken", not "nobody does > > that"). > > I don't know about "lots" of code, but it will break at least o

Re: [Python-Dev] python build failed on mac

Hello Vijay Am Freitag, 20. Januar 2012 um 00:56 schrieb Vijay N. Majagaonkar: > I am trying to build python 3 on mac and build failing with following error > can somebody help me with this It is a known bug that Apple's latest gcc-llvm (that comes with Xcode 4.1 by default as gcc) miscompile

Re: [Python-Dev] python build failed on mac

Am Freitag, 20. Januar 2012 um 23:40 schrieb Vijay Majagaonkar: > > > I am trying to build python 3 on mac and build failing with following > > > error can somebody help me with this > > > > It is a known bug that Apple's latest gcc-llvm (that comes with Xcode 4.1 > > by default as gcc) miscompi

Re: [Python-Dev] PEP 408 -- Standard library __preview__ package

Hi, Am 27.01.2012 um 18:26 schrieb Alex: > I'm -1 on this, for a pretty simple reason. Something goes into __preview__, > instead of it's final destination directly because it needs feedback/possibly > changes. However, given the release cycle of the stdlib (~18 months), any > feedback it gets ca

Re: [Python-Dev] PEP 414

Hi Ezio, Am 02.03.2012 um 10:33 schrieb Ezio Melotti: >> [quoting Armin from Reddit] >> "Because in all honesty, because string wrappers make a codebase horrible to >> work with. I will have to continue maintaining 2.x versions for at least >> another >> four or five years. The idea if having to

Re: [Python-Dev] PEP 414

Am 02.03.2012 um 20:44 schrieb Barry Warsaw: >> 3.3 is the IMHO the first 3.x release that brings really cool stuff to the >> table and might be the tipping point for people to start embracing Python 3 – >> despite the fact that Ubuntu LTS will alas ship 3.2 for the next 10 years. I >> hope for s

Re: [Python-Dev] Playing with a new theme for the docs, iteration 2

Hi Georg, Am 25.03.2012 um 08:34 schrieb Georg Brandl: > Here's another try, mainly with default browser font size, more contrast and > collapsible sidebar again: > > http://www.python.org/~gbrandl/build/html2/ I really like it! Only one nitpick: If a header follows on a “seealso”, the vertica

Re: [Python-Dev] docs.python.org pointing to Python 3 by default?

Hi, > At what point should we cut over docs.python.org to point to the > Python 3 documentation by default? Wouldn't this be an easy bit to > flip in order to promote Python 3 more better? I’d vote for the release of 3.3 instead of a surprise change in the middle of nowhere. Cheers, Hynek _

[Python-Dev] Backward compatibility of shutil.rmtree

Hi, as our shutil.rmtree() is vulnerable to symlink attacks (see ) I’ve implemented a safe version using os.fwalk() and os.unlinkat() for Python 3.3. Now we face a problem I’d like a broad opinion on: rmtree has a callback hook called `onerror` that that gets cal

Re: [Python-Dev] Backward compatibility of shutil.rmtree

>> Two of them differ in the new version: os.fwalk() is used instead of >> os.listdir() and os.unlinkat() instead of os.remove(). > It would be os.flistdir instead of os.listdir, not os.fwalk, right? It’s actually os.fwalk. It has been implemented by Charles-François as a dependency of the ticket

Re: [Python-Dev] Backward compatibility of shutil.rmtree

Am 20.05.12 23:46, schrieb mar...@v.loewis.de: Two of them differ in the new version: os.fwalk() is used instead of os.listdir() and os.unlinkat() instead of os.remove(). >>> It would be os.flistdir instead of os.listdir, not os.fwalk, right? >> It’s actually os.fwalk. It has been implem

Re: [Python-Dev] docs.python.org pointing to Python 3 by default?

>>> Namespaces are a great idea, let's do more of those :) >> A subdomain isn't a namespace? > A subdomain is only a namespace if you use it as one. The following > would be using docs.python.org as a namespace (and is what I think we > should move towards): > > docs.python.org/latest > docs.pyth

Re: [Python-Dev] docs.python.org pointing to Python 3 by default?

>> Also -1 on docs3, that would suggest that it’s still something special >> and 2 (= docs) is the real deal. > Guido and I are proposing docs2 and docs3 each pointing to the latest > docs for each series. That puts them on equal status. > docs.python.org, besides being a namespace for specific ver

Re: [Python-Dev] [Python-checkins] cpython (2.7): #14804: Remove [] around optional arguments with default values

Hi Nick, >> Mostly just mechanical removal of []. In some rare cases I've pulled the >> default value up into the argument list. > Be a little careful with this - "[]" is the right notation when the > function doesn't support keyword arguments. At least one of the > updated signatures is incorrect

Re: [Python-Dev] whither PEP 407 and 413 (release cycle PEPs)?

Am 03.06.12 13:22, schrieb "Martin v. Löwis": > - Some contributors are worried about getting their contributions "out", > and some core committers are worried that we get fewer contributions > because of that. > > While I well recall the feeling of getting changes "out", the real > conce

Re: [Python-Dev] Status of packaging in 3.3

On 06/20, Antoine Pitrou wrote: > Let's make things clear: packaging is suffering from a lack of > developer involvement, Absolutely. And to be more precise: solid hands-on leadership. Eric wrote it in his original mail: both packaging maintainers are burned out/busy. That’s a state that is ve

Re: [Python-Dev] [Python-checkins] cpython: #4489: Add a shutil.rmtree that isn't suspectible to symlink attacks

>> It is used automatically on platforms supporting the necessary os.openat() >> and >> os.unlinkat() functions. Main code by Martin von Löwis. > > Unfortunately, this isn't actually having any effect at the moment > since the os module APIs changed for the beta release. > > The "hasattr(os, 'un

Re: [Python-Dev] Signed packages

Am 23.06.12 14:03, schrieb mar...@v.loewis.de: >> I'm surprised gpg hasn't been mentioned here. I think these are all >> solved problems, most free software that is signed signs it with the >> gpg key of the author. In that case all that is needed is that the >> cheeseshop allows the uploading o

Re: [Python-Dev] [Infrastructure] Buildbot master moved

Hi, I don’t know if it’s known, but the bot infrastructure is FUBAR now. http://buildbot.python.org/all/waterfall is a stacktrace and all tests fail because of the XML-RPC tests that use our buildbot API. Regards Hynek ___ Python-Dev mailing list Python

Re: [Python-Dev] [Infrastructure] Buildbot master moved

> Now someone needs to incorporate these changes into our local git. I'm a > git newbie, and basic commands seem to fail for me: > > $ git fetch -v > Permission denied (publickey). > fatal: The remote end hung up unexpectedly > > Hynek, do you want to help? I'd love to, but I'm afk for the rest

Re: [Python-Dev] Proposed schedule for Python 3.4

Am 04.10.2012 um 03:38 schrieb R. David Murray : >>> Other proposed large-scale changes: >>> [...] >>> * A standard event-loop interface (PEP by Jim Fulton pending) >> >> Really? Was this discussed somewhere? I'd like to know more about it. > > I believe it was discussed at the Language Summit

Re: [Python-Dev] [Python-checkins] cpython (merge 3.3 -> default): Merge issue #15936: Add link from os.urandom to random.SystemRandom

Am 16.10.2012 um 12:15 schrieb andrew.svetlov : > + For easy to use interface to system randomness please see > + :class:`random.SystemRandom`. Is it just my non-native speaker ears, or should there be an “an” before “easy”? ___ Python-Dev mailing l

Re: [Python-Dev] Python 3.3 vs. Python 2.7 benchmark results (again, but this time more solid numbers)

Am 28.10.2012 um 12:11 schrieb Antoine Pitrou : >> One word: profile. >> >> Looking at stat counts alone rather than measuring the total time spent in >> all types of system calls from strace and profiling is not really useful. ;) > Agreed, but I can't seem to cope properly with gprof. Any sugge

Re: [Python-Dev] Proposing "Argument Clinic", a new way of specifying arguments to builtins for CPython

Am 04.12.2012 um 00:42 schrieb Gregory P. Smith : > * How would we convert all the builtins to use Clinic? I fear any > solution will involve some work by hand. Even if we can automate > big chunks of it, fully automating it would require parsing arbitrary > C. This seems like overkill fo