Am 15.05.14 16:20, schrieb Skip Montanaro:
On Thu, May 15, 2014 at 8:26 AM, Antoine Pitrou solip...@pitrou.net wrote:
We already have such buildbots, they are in the unstable category.
You can browse through existing buildbots here:
https://www.python.org/dev/buildbot/
I can't see how to
Am 14.05.14 16:28, schrieb Barry Warsaw:
On May 14, 2014, at 02:20 PM, Brett Cannon wrote:
Do we want an official policy written down in a PEP (yes, I can write it)?
Should I keep closing these patches and saying that we are not adding
support for new operating systems and be hand-wavy about
Greetings Python users,
Python 2.7.7 release candidate 1 is now available for download. Python
2.7.7 is a regularly scheduled bugfix release for the Python 2.7 series.
The 2.7.7 release contains fixes for two severe, if arcane, potential
security vulnerabilities. The first was the possibility of
On Sun, May 18, 2014 at 5:49 PM, Benjamin Peterson benja...@python.orgwrote:
Greetings Python users,
Python 2.7.7 release candidate 1 is now available for download. [...]
http://hg.python.org/cpython/raw-file/e32e3a9f3902/Misc/NEWS
So what became of PEP 466? This Misc/NEWS only mentions
On Sun, May 18, 2014, at 18:53, Guido van Rossum wrote:
On Sun, May 18, 2014 at 5:49 PM, Benjamin Peterson
benja...@python.orgwrote:
Greetings Python users,
Python 2.7.7 release candidate 1 is now available for download. [...]
On Sun, May 18, 2014, at 18:53, Guido van Rossum wrote:
On Sun, May 18, 2014 at 5:49 PM, Benjamin Peterson
benja...@python.orgwrote:
Greetings Python users,
Python 2.7.7 release candidate 1 is now available for download. [...]
On Sun, May 18, 2014, at 18:53, Guido van Rossum wrote:
On Sun, May 18, 2014 at 5:49 PM, Benjamin Peterson
benja...@python.orgwrote:
Greetings Python users,
Python 2.7.7 release candidate 1 is now available for download. [...]
On May 18, 2014, at 9:53 PM, Guido van Rossum gu...@python.org wrote:
On Sun, May 18, 2014 at 5:49 PM, Benjamin Peterson benja...@python.org
wrote:
Greetings Python users,
Python 2.7.7 release candidate 1 is now available for download. [...]
Thanks for the update, Donald. Did anyone get any help from Red Hat or
other distros?
On Sun, May 18, 2014 at 7:02 PM, Donald Stufft don...@stufft.io wrote:
On May 18, 2014, at 9:53 PM, Guido van Rossum gu...@python.org wrote:
On Sun, May 18, 2014 at 5:49 PM, Benjamin Peterson
Well I believe Alex did what he did during his work day @ Rackspace.
Distros specifically I don’t believe so, although both Alex and myself agreed
that it
made sense for the SSL changes to wait until after the other changes since it
was
the largest and most complicated. I think that’s the one
At the very least PEP 466 needs to be updated to admit the failure -- it
would be a shame if people read the PEP and assumed the promised features
actually landed in 2.7.7 (which the PEP explicitly lists).
___
Python-Dev mailing list
On 19 May 2014 12:35, Guido van Rossum gu...@python.org wrote:
At the very least PEP 466 needs to be updated to admit the failure -- it
would be a shame if people read the PEP and assumed the promised features
actually landed in 2.7.7 (which the PEP explicitly lists).
Will do - I'll update
An hour ago, I pulled recent commits to my local repository.
I edited a couple of files, wrote commit messages, and pulled again,
nothing new. I then did the usual: commit 2.7, commit 3.4, merge to 3.5.
Problem: merge conflicts from 6 files I have never touched.
Include/patchlevel.h
On May 19, 2014, at 5:52 AM, Terry Reedy tjre...@udel.edu wrote:
I stopped at this point and ran diskcheck. I then looked at the DAG and
noticed 5 previous 3.4 patches that were not merged into 3.5: rev 90750 and
90751, Larry Hastings, 2 weeks ago!, rev
90752 and 90753 by Larry a day ago,
14 matches
Mail list logo
