On behalf of the Python development community, I'm plesed to announce
the availability of Python 3.5.10.
Python 3.5 is in "security fixes only" mode. This new version only
contains security fixes, not conventional bug fixes, and it is a
source-only release.
Important Notice: The latest re
On behalf of the Python development community, I'm pleased to finally
announce the availability of Python 3.5.10rc1.
Python 3.5 is in "security fixes only" mode. This new version only
contains security fixes, not conventional bug fixes, and it is a
source-only release.
Important Notice: T
On behalf of the Python development community, I'm slightly chagrined to
announce the availability of Python 3.5.9. There were no new changes in
version 3.5.9; 3.5.9 was released only because of a CDN caching problem,
which resulted in some users downloading a prerelease version of the
3.5.8
Due to awkward CDN caching, some users who downloaded the source code
tarballs of Python 3.5.8 got a preliminary version instead of the final
version. As best as we can tell, this only affects the .xz release;
there are no known instances of users downloading an incorrect version
of the .tgz
On behalf of the Python development community, I'm relieved to announce
the availability of Python 3.5.8.
Python 3.5 is in "security fixes only" mode. This new version only
contains security fixes, not conventional bug fixes, and it is a
source-only release.
You can find Python 3.5.8 here
On behalf of the Python development community, I'm relieved to announce
the availability of Python 3.5.8rc2. It's been a month after Python
3.5.8rc1, and since then we've added a small amount of new code to fix
an API-level regression in http client, updated expat to 2.2.8, and
upgraded the
On behalf of the Python development community, I'm chuffed to announce
the availability of Python 3.5.8rc1.
Python 3.5 is in "security fixes only" mode. This new version only
contains security fixes, not conventional bug fixes, and it is a
source-only release.
You can find Python 3.5.8rc1
It's with a note of sadness that I announce the final retirement of
Python 3.4. The final release was back in March, but I didn't get
around to actually closing and deleting the 3.4 branch until this morning.
Python 3.4 introduced many features we all enjoy in modern Python--the
asyncio, en
On behalf of the Python development community, I'm proud--if slightly
sad--to announce the availability of Python 3.4.10.
Python 3.4.10 was released in "security fixes only" mode. It only
contains security fixes, not conventional bug fixes, and it is a
source-only release.
Python 3.4.10 i
On behalf of the Python development community, I'm chuffed to announce
the availability of Python 3.5.7.
Python 3.5 is in "security fixes only" mode. It only accepts security
fixes, not conventional bug fixes, and the release is source-only.
And you can find Python 3.5.7rc1 here:
https
On behalf of the Python development community, I'm chuffed to announce
the availability of Python 3.4.10rc1 and Python 3.5.7rc1.
Both Python 3.4 and 3.5 are in "security fixes only" mode. Both
versions only accept security fixes, not conventional bug fixes, and
both releases are source-only
On behalf of the Python development community, I'm happy to announce the
availability of Python 3.4.9 and Python 3.5.6.
Both Python 3.4 and 3.5 are in "security fixes only" mode. Both
versions only accept security fixes, not conventional bug fixes, and
both releases are source-only.
You
On behalf of the Python development community, I'm pleased to announce
the availability of Python 3.4.9rc1 and Python 3.5.6rc1.
Both Python 3.4 and 3.5 are in "security fixes only" mode. Both
versions only accept security fixes, not conventional bug fixes, and
both releases are source-only.
Actually, it was updated on the server, but somehow the old version was
sticking around in the CDN cache. I "purged" it and it's fine now.
Weird that it would linger this long!
Cheers,
//arry/
On 02/10/2018 03:20 AM, Serhiy Storchaka wrote:
05.02.18 02:35, Larry Ha
Actually, it was updated on the server, but somehow the old version was
sticking around in the CDN cache. I "purged" it and it's fine now.
Weird that it would linger this long!
Cheers,
//arry/
On 02/10/2018 03:20 AM, Serhiy Storchaka wrote:
05.02.18 02:35, Larry Ha
On behalf of the Python development community, I'm happy to announce the
availability of Python 3.4.8 and Python 3.5.5.
Both Python 3.4 and 3.5 are in "security fixes only" mode. Both
versions only accept security fixes, not conventional bug fixes, and
both releases are source-only.
You
On behalf of the Python development community, I'm pleased to announce
the availability of Python 3.4.8rc1 and Python 3.5.5rc1.
Both Python 3.4 and 3.5 are in "security fixes only" mode. Both versions
only accept security fixes, not conventional bug fixes, and both
releases are source-only.
On behalf of the Python development community and the Python 3.4 release
team, I'm pleased to announce the availability of Python 3.4.7.
Python 3.4 is now in "security fixes only" mode. This is the final
stage of support for Python 3.4. Python 3.4 now only receives security
fixes, not bug
On behalf of the Python development community and the Python 3.5 release
team, I'm pleased to announce the availability of Python 3.5.4.
Python 3.5.4 is the final 3.5 release in "bug fix" mode. The Python
3.5 branch has now transitioned into "security fixes mode"; all future
improvements i
On behalf of the Python development community and the Python 3.4 and
Python 3.5 release teams, I'm relieved to announce the availability of
Python 3.4.7rc1 and Python 3.5.4rc1.
Python 3.4 is now in "security fixes only" mode. This is the final
stage of support for Python 3.4. Python 3.4 no
On behalf of the Python development community and the Python 3.4 and
Python 3.5 release teams, I'm delighted to announce the availability of
Python 3.4.6 and Python 3.5.3.
Python 3.4 is now in "security fixes only" mode. This is the final
stage of support for Python 3.4. Python 3.4 now onl
On behalf of the Python development community and the Python 3.4 and
Python 3.5 release teams, I'm pleased to announce the availability of
Python 3.4.6rc1 and Python 3.5.6rc1.
Python 3.4 is now in "security fixes only" mode. This is the final
stage of support for Python 3.4. Python 3.4 now
On behalf of the Python development community and the Python 3.4 and
Python 3.5 release teams, I'm pleased to announce the availability of
Python 3.4.5rc1 and Python 3.5.2rc1.
Python 3.4 is now in "security fixes only" mode. This is the final
stage of support for Python 3.4. All changes ma
On behalf of the Python development community and the Python 3.4 release
team, I'm pleased to announce the availability of Python 3.4.4. Python
3.4.4 is the last version of Python 3.4.4 with binary installers, and
the end of "bugfix" support. After this release, Python 3.4.4 moves
into "sec
On behalf of the Python development community and the Python 3.4 and 3.5
release teams, I'm pleased to announce the simultaneous availability of
Python 3.5.1 and Python 3.4.4rc1. As point releases, both have many
incremental improvements over their predecessor releases.
You can find Pytho
On behalf of the Python development community and the Python 3.5 release
team, I'm pleased to announce the availability of Python 3.5.1rc1.
Python 3.5.1 will be the first update for Python 3.5. Python 3.5 is the
newest version of the Python language, and it contains many exciting new
featur
On behalf of the Python development community and the Python 3.5 release
team, I'm proud to announce the availability of Python 3.5.0. Python
3.5.0 is the newest version of the Python language, and it contains many
exciting new features and optimizations.
You can read all about what's new
On behalf of the Python development community and the Python 3.5 release
team, I'm surprised to announce the availability of Python 3.5.0rc4,
also known as Python 3.5.0 Release Candidate 4.
Python 3.5.0 Release Candidate 3 was only released about a day ago.
However: during testing, a major
On behalf of the Python development community and the Python 3.5 release
team, I'm relieved to announce the availability of Python 3.5.0rc3, also
known as Python 3.5.0 Release Candidate 3.
The next release of Python 3.5 will be Python 3.5.0 final. There should
be few (or no) changes to Pyt
On behalf of the Python development community and the Python 3.5 release
team, I'm relieved to announce the availability of Python 3.5.0rc2, also
known as Python 3.5.0 Release Candidate 2.
Python 3.5 has now entered "feature freeze". By default new features
may no longer be added to Python
I built the source tarballs with a slightly-out-of-date tree. We
slipped the release by a day to get two fixes in, but the tree I built
from didn't have those two fixes.
I yanked the tarballs off the release page as soon as I suspected
something. I'm rebuilding the tarballs and the docs n
On 08/10/2015 05:55 PM, Larry Hastings wrote:
I yanked the tarballs off the release page as soon as I suspected
something. I'm rebuilding the tarballs and the docs now. If you
grabbed the tarball as soon as it appeared, it's slightly out of date,
please re-grab.
p.s. I s
On behalf of the Python development community and the Python 3.5 release
team, I'm relieved to announce the availability of Python 3.5.0rc1, also
known as Python 3.5.0 Release Candidate 1.
Python 3.5 has now entered "feature freeze". By default new features
may no longer be added to Python
On behalf of the Python development community and the Python 3.5 release
team, I'm delighted to announce the availability of Python 3.5.0b4. Python
3.5.0b4 is scheduled to be the last beta release; the next release will be
Python 3.5.0rc1, or Release Candidate 1.
Python 3.5 has now entered "featu
On behalf of the Python development community and the Python 3.5 release
team, I'm relieved to announce the availability of Python 3.5.0b3.
Python 3.5 has now entered "feature freeze". By default new features
may no longer be added to Python 3.5.
This is a preview release, and its use is
On behalf of the Python development community and the Python 3.5 release
team, I'm relieved to announce the availability of Python 3.5.0b2.
Python 3.5.0b1 had a major regression (see
http://bugs.python.org/issue24285 for more information) and as such was
not suitable for testing Python 3.5.
On behalf of the Python development community and the Python 3.5 release
team, I'm pleased to announce the availability of Python 3.5.0b1.
Python 3.5 has now entered "feature freeze". By default new features may
no longer be added to Python 3.5. (However, there are a handful of
features tha
On behalf of the Python development community and the Python 3.5 release
team, I'm thrilled to announce the availability of Python 3.5.0a4.
Python 3.5.0a4 is the fourth and alpha release of Python 3.5, which will
be the next major release of Python. Python 3.5 is still under
development, a
On behalf of the Python development community and the Python 3.5 release
team, I'm thrilled to announce the availability of Python 3.5.0a3.
Python 3.5.0a3 is the third alpha release of Python 3.5, which will be
the next major release of Python. Python 3.5 is still under heavy
development,
On behalf of the Python development community and the Python 3.5 release
team, I'm thrilled to announce the availability of Python 3.5.0a2.
Python 3.5.0a2 is the second alpha release of Python 3.5, which will be
the next major release of Python. Python 3.5 is still under heavy
development
On behalf of the Python development community and the Python 3.4 release
team, I'm pleased to announce the availability of Python 3.4.3. Python
3.4.3 has many bugfixes and other small improvements over 3.4.2.
You can find it here:
https://www.python.org/downloads/release/python-343/
On 02/08/2015 02:06 PM, Mark Lawrence wrote:
On 08/02/2015 22:00, Larry Hastings wrote:
On behalf of the Python development community and the Python 3.4 release
team, I'm happy to announce the availability of Python 3.4.3rc1.
Python 3.4.3rc1 has many bugfixes and other small improvements
On behalf of the Python development community and the Python 3.5 release
team, I'm also pleased to announce the availability of Python 3.5.0a1.
Python 3.5.0a1 is the first alpha release of Python 3.5, which will be
the next major release of Python. Python 3.5 is still under heavy
developm
On behalf of the Python development community and the Python 3.4 release
team, I'm happy to announce the availability of Python 3.4.3rc1.
Python 3.4.3rc1 has many bugfixes and other small improvements over 3.4.2.
You can download it here:
https://www.python.org/download/releases/3.4.3
On behalf of the Python development community and the Python 3.4 release
team, I'm pleased to announce the availability of Python 3.4.2. Python
3.4.2 has many bugfixes and other small improvements over 3.4.1. One
new feature for Mac OS X users: the OS X installers are now distributed
as sig
/issue21431
We'll get it right for 3.4.2 final. I don't think we need to respin
3.4.2rc1 / add a 3.4.2rc2 for this.
On 09/22/2014 06:02 PM, Terry Reedy wrote:
On 9/22/2014 10:15 AM, Larry Hastings wrote:
You can download it here:
https://www.python.org/download/rele
On behalf of the Python development community and the Python 3.4 release
team, I'm chuffed to announce the availability of Python 3.4.2rc1.
Python 3.4.2 has many bugfixes and other small improvements over 3.4.1.
One new feature for Mac OS X users: the OS X installers are now
distributed as
On behalf of the Python development community and the Python 3.4 release
team, I'm pleased to announce the availability of Python 3.4.1. Python
3.4.1 has over three hundred bugfixes and other improvements over 3.4.0.
One notable change: the version of OpenSSL bundled with the Windows
instal
On behalf of the Python development community and the Python 3.4 release
team, I'm pleased to announce the availability of Python 3.4.1rc1.
Python 3.4.1rc1 has over three hundred bugfixes and other improvements
over 3.4.0. One notable change: the version of OpenSSL bundled with the
Windows
ved protocol for pickled objects
* PEP 3156, a new "asyncio" module, a new framework for asynchronous I/O
To download Python 3.4.0 visit:
http://www.python.org/download/releases/3.4.0/
This is a production release. Please report any issues you notice to:
http://bugs.python
ill be
added. The final release is projected for March 16, 2014.
To download Python 3.4.0rc3 visit:
http://www.python.org/download/releases/3.4.0/
Please consider trying Python 3.4.0rc3 with your code and reporting any
new issues you notice to:
http://bugs.python.org/
Enjoy!
**
rg/download/releases/3.4.0/
Once I can update the new web site, Python 3.4.0rc2 will be available here:
http://python.org/download/releases/
(I'm not sure what the final URL will be, but you'll see it listed on
that page.)
Please consider trying Python 3.4.0rc2 with your code an
he final release is projected for mid-March 2014.
To download Python 3.4.0rc1 visit:
http://www.python.org/download/releases/3.4.0/
Please consider trying Python 3.4.0rc1 with your code and reporting any
new issues you notice to:
http://bugs.python.org/
Enjoy!
--
Larry Hastings,
he final release is projected for mid-March 2014.
To download Python 3.4.0b3 visit:
http://www.python.org/download/releases/3.4.0/
Please consider trying Python 3.4.0b3 with your code and reporting any
new issues you notice to:
http://bugs.python.org/
Enjoy!
--
Larry Hastings, Rel
inal release is projected for late February 2014.
To download Python 3.4.0b2 visit:
http://www.python.org/download/releases/3.4.0/
Please consider trying Python 3.4.0b2 with your code and reporting any
new issues you notice to:
http://bugs.python.org/
Enjoy!
--
Larry Hastings, Rel
On 11/24/2013 02:00 PM, Larry Hastings wrote:
Python 3.4 includes a range of improvements of the 3.x series, including
hundreds of small improvements and bug fixes. Major new features and
changes in the 3.4 release series include:
Whoops, sorry, I missed a couple of PEPs there:
* PEP 428, a
e", meaning that no new features will be
added. The final release is projected for late February 2014.
To download Python 3.4.0b1 visit:
http://www.python.org/download/releases/3.4.0/
Please consider trying Python 3.4.0b1 with your code and reporting any
new issues you notice to:
ule test suite fails on some platforms.
* I/O conducted by the "asyncio" module may, rarely,
erroneously time out. The timeout takes one hour.
Please consider trying Python 3.4.0a4 with your code and reporting any
new issues you notice to:
http://bugs.python.org/
Enjoy!
--
La
s you notice to:
http://bugs.python.org/
Enjoy!
--
Larry Hastings, Release Manager
larry at hastings.org
(on behalf of the entire python-dev team and 3.4's contributors)
--
https://mail.python.org/mailman/listinfo/python-list
On 09/09/2013 09:30 PM, Antoine Pitrou wrote:
Le Mon, 9 Sep 2013 08:16:06 -0400,
Brett Cannon a écrit :
Those last two PEPs are still in draft form and not accepted nor have
any committed code yet.
Unless Larry enthusiastically sneaked them into the release.
Whoops. Nope, I'm not that enthu
isit:
http://www.python.org/download/releases/3.4.0/
Please consider trying Python 3.4.0a2 with your code and reporting any
issues you notice to:
http://bugs.python.org/
Enjoy!
--
Larry Hastings, Release Manager
larry at hastings.org
(on behalf of the entire python-dev team and 3.4's co
Does anybody have an email address (or anything, really) for Jim
Hugunin? He left Google in May and appears to have dropped off the face
of the internet. Please email me privately.
I swear I will use the information only for good and never for evil,
//arry/
--
http://mail.python.org/mai
Radio Free Python is a new monthly podcast focused on Python and its
community.
Episode 1 has just been released! It features a panel discussion with
the PythonLabs team:
* Barry Warsaw,
* Fred Drake,
* Guido van Rossum,
* Roger Masse,
* and Tim Peters.
You can find it at
On 04/13/2011 07:37 PM, Eric Snow wrote:
I suppose you could try something like this:
class Outer:
global Inner
class Inner:
class Worker:
pass
class InnerSubclass(Inner):
class Worker(Inner.Worker):
pass
However, that pollutes your global namespace. If you are worr
The problem: if you're currently in a nested class, you can't look up
variables in the outer "class scope".
For example, this code fails in Python 3:
class Outer:
class Inner:
class Worker:
pass
class InnerSubclass(Inner):
class Worker(Inner.Worker):
I'm doing a talk at PyCon about changes to the Python language. I'm
wondering: are there any Python language changes that first shipped in
an implementation of Python besides CPython?
The sort of answer I'm looking for: "set literals first shipped in
Jython 2.2, six months before they ship
In article
,
Benjamin Kaplan wrote:
wxpython installs a "wxversion" module which has functions like
getInstalled(), ensureMinimal(version), and select(version). You can
call wxversion.select before importing wx and it will make sure that
the correct version is imported. You might want to
I'm writing a package for Python 3--let's call it "spacegoblin". I fear someday I may need
multiple versions installed and available simultaneously, even within one version of Python. So I want to
plan ahead for that possibility. What would be the best way to allow this? Right now I install
norseman wrote:
"...This patch changes "ntpath" ..."changing or adding to such a
module which is OS specific is fine with me.
[...]
To point it bluntly: How does one use "F:" in Linux in the identical
fashion as a MicroSoft OS?
Sorry, I assumed this was common knowledge: os.path is impl
There are some PEPs that seem to be stuck in a perpetual limbo, never to
be decided upon. Some of them seem hopelessly antiquated now--they were
proposed long ago and the language has moved on. With every passing day
it becomes less likely they will ever be Accepted.
On the off chance tha
I've written a patch for Python 3.1 that changes os.path so it handles
UNC paths on Windows. You can read about it at the Python bug tracker:
http://bugs.python.org/issue5799
I'd like to gauge community interest in the patch. After all, it's has
been declined before; I submitted a simi
I'm working on a patch or two for Python. Now, it's always best to use
a source code manager (rcs, whatever) when writing code; in particular
it'd make updating to the latest Python trees much easier. But I don't
have write access to the Python Subversion repository. So I figured
out how to wo
Nicko wrote:
> I note that in both of those tests you didn't actually ever realise the
> concatenated string. Can you give us figures for these tests having
> forced the concatenated string to be computed?
Sure, good call. And bad news.
All these benchmarks were with functions taking N argument
Istvan Albert wrote:
> I remember a similar patch from some time ago:
> > http://mail.python.org/pipermail/python-dev/2004-August/046686.html
That patch addressed the same general problem, but took a completely
different approach. For the record, this patch (#980695) optimized "x
+= a" by examini
John Machin wrote:
> Don't you mean y = x[1] or something like that? y = "".join(x) looks
> like a copy-paste error.
You're right, by gum. Worse than that, my benchmark wasn't actually
*doing* much of anything there; at the end of the run x was still
length 0. That was sloppy, and I apologize.
Fredrik Lundh wrote:
> You should also benchmark this against code that uses the ordinary
> append/join pattern.
Sorry, thought I had. Of course, now that the patch is up on
Sourceforce you could download it and run all the benchmarks you like.
For all the benchmarks I ran below, the number list
An update: I have submitted this as a patch on SourceForge.
It's request ID #1569040.
http://sourceforge.net/tracker/?group_id=5470&atid=305470
I invite everyone to take it for a spin!
There are some improvements in this version. Specifically:
* Python will no longer crash if you do ten
Fredrik Lundh wrote:
> so what does the benchmark look like if you actually do this ?
Okay, timing this:
x = ""
for i in range(10):
x += "a"
t = x[1] # forces the concat object to render
The result:
Python 2.5 release: 30.0s
Python 2.5 locally built: 30.2s
Python 2.5 concat: 4
Fredrik Lundh wrote:
> >> what's in "s" when that loop is done?
> > It's equivalent to " 'a' * 1000 ". (I shan't post it here.)
> but what *is* it ? an ordinary PyString object with a flattened buffer,
> or something else ?
At the exact moment that the loop is done, it's a
PyStringConcatenat
William Heymann wrote:
> This is a pretty small change but I would suggest xrange instead of range.
Good point! Since I was calling range() during the benchmark, it was
timed too. Switching to xrange() will mean less overhead.
I re-ran this benchmark (again):
s = ""
for i in range(10):
Fredrik Lundh wrote:
> > Sure. Here are the results, but with range (1000):
> ten million? what hardware are you running this on?
Athlon 64 x2 4400+ (aka 2.2GHz), 3GB of RAM, Windows XP.
> what's in "s" when that loop is done?
It's equivalent to " 'a' * 1000 ". (I shan't post it here
Steve Holden wrote:
> you should diff your source against the current
> SVN repository and lodge that diff as a patch on SourceForge.
Okay, I'll try to do that today.
> Your suggested bug isn't, I think a real bug in the current
> implementation because as I understand it Python strings do alwa
This is such a long posting that I've broken it out into sections.
Note that while developing this patch I discovered a Subtle Bug
in CPython, which I have discussed in its own section below.
THE OVERVIEW
I don't remember where I picked it up, but I remember reading years
ago that th
Delaney, Timothy (Tim) wrote:
> Could you raise this as a bug on Sourceforge?
Done; it is "request ID" 1526203.
https://sourceforge.net/tracker/index.php?func=detail&aid=1526203&group_id=5470&atid=105470
Cheers,
/larry/
--
http://mail.python.org/mailman/listinfo/python-list
I run the following script:
--
from subprocess import *
Popen("ls -l")
--
(yeah, I have ls.exe on Windows)
Under Python 2.4.2, this simply dumped the results of ls.exe to the
terminal--sorry, to the "command shell".
Under Python 2.5, both beta 1 and beta 2, it dumps the results to the
command she
> Are you willing to monitor and fix new Py_USING_UNICODE issues or
> are you proposing just to produce a patch now and then expect
> contributors to maintain this feature?
Neither, I suppose, or perhaps both. I am proposing to produce a patch
now which fixes the non-Unicode build under Windows.
There are exactly four non-Unicode build breakages in the Python source
tree that are Win32-specific. Two are simply a matter of #if, two also
require new alternative code (calls to PyString_FromStringAndSize()).
All told, my changes to Win32-specific code to fix Py_USING_UNICODE
consists of exact
I'm an indie shareware Windows game developer. In indie shareware
game development, download size is terribly important; conventional
wisdom holds that--even today--your download should be 5MB or less.
I'd like to use Python in my games. However, python24.dll is 1.86MB,
and zips down to 877k. I
I finally got 'round to installing Python 2.4. I'm planning on using
Python for downloadable software, where every kilobyte counts and
smaller is definitely better. Imagine my surprise when I looked up
python24.dll and found SWEET JUMPING CHRISTMAS it's ballooned up to
1.8MB!
This isn't a deal-k
89 matches
Mail list logo
