On behalf of the Python development team, I'm happy to announce the
first beta release of Python 3.3.0.
This is a preview release, and its use is not recommended in
production settings.
Python 3.3 includes a range of improvements of the 3.x series, as well
as easier porting between 2.x and 3.x.
On 06/26/2012 11:10 PM, Georg Brandl wrote:
On behalf of the Python development team, I'm happy to announce the
first beta release of Python 3.3.0.
I 3 3.3
Thanks Georg! And everybody who contributed.
Stoked,
//arry/
___
Python-Dev mailing list
On Wed, Jun 27, 2012 at 01:49:34AM +0200, Giampaolo Rodol? g.rod...@gmail.com
wrote:
I've just noticed a strange behavior when dealing with gvfs filesystems:
giampaolo@ubuntu:~$ python -c import os;
print(os.path.exists('/home/giampaolo/.gvfs'))
True
giampaolo@ubuntu:~$ sudo su
All,
Congradulations. This is a big one!
On Wed, Jun 27, 2012 at 2:10 AM, Georg Brandl ge...@python.org wrote:
On behalf of the Python development team, I'm happy to announce the
first beta release of Python 3.3.0.
This is a preview release, and its use is not recommended in
production
Hi,
Here is an informational PEP proposal:
http://hg.python.org/peps/file/52767ab7e140/pep-0423.txt
Could you review it for style, consistency and content?
Additional notes:
* Original discussion posted to distutils-...@python.org
* started on May 2012 at
Hello,
On Wed, 27 Jun 2012 11:08:45 +0200
Benoît Bryon ben...@marmelune.net wrote:
Hi,
Here is an informational PEP proposal:
http://hg.python.org/peps/file/52767ab7e140/pep-0423.txt
Could you review it for style, consistency and content?
There is one Zen principle this PEP is missing:
I thought the PEP actually covered it pretty well:
- if you don't want to worry about name conflicts for every module, pick
*one* short top level namespace for your group and use that
- for shared modules, use the top level namespace with PyPI as the name
registry
It's reasonable advice when
On Wed, 27 Jun 2012 21:19:57 +1000
Nick Coghlan ncogh...@gmail.com wrote:
I thought the PEP actually covered it pretty well:
- if you don't want to worry about name conflicts for every module, pick
*one* short top level namespace for your group and use that
- for shared modules, use the top
On 27 June 2012 12:34, Antoine Pitrou solip...@pitrou.net wrote:
On Wed, 27 Jun 2012 21:19:57 +1000
Nick Coghlan ncogh...@gmail.com wrote:
I thought the PEP actually covered it pretty well:
- if you don't want to worry about name conflicts for every module, pick
*one* short top level
Am 27.06.2012 01:49, schrieb Giampaolo Rodolà:
I've just noticed a strange behavior when dealing with gvfs filesystems:
giampaolo@ubuntu:~$ python -c import os;
print(os.path.exists('/home/giampaolo/.gvfs'))
True
giampaolo@ubuntu:~$ sudo su
root@ubuntu:~# python -c import os;
On 27/06/12 02:19:03, Giampaolo Rodolà wrote:
2012/6/27 Cameron Simpson c...@zip.com.au:
So I'd be +0.5 for making the docs more clear that True is reliable and
False may merely mean could not access.
+1
+1
I was about to propose a 'strict' parameter which lets the exception
propagate in
On 26/06/2012 20:02, Terry Reedy wrote:
On 6/26/2012 6:51 AM, Devin Jeanpierre wrote:
The issue is that sometimes, if you press ctrl-c on Windows, instead
of raising a KeyboardInterrupt, Python will exit completely. Because
of this, any program that relies on ctrl-c/KeyboardInterrupt is not
On 27 June 2012 13:20, Paul Moore p.f.mo...@gmail.com wrote:
I agree. I only skimmed the PEP, but even on a skimming, I got the
impression that it was promoting the use of namespaces for ownership,
in a Java-like way. The part Nick quoted is substantially more
reasonable (assuming that's a
I can confirm that there is a race condition between the code in
myreadline.c and the signal_handler. I have a patch in readiness which
basically loops until the signal has been tripped.
But what I don't know is: what to do if the signal *still* doesn't trip
(after 100 millisecond-retries)?
On 2012-06-27, at 10:57 AM, Paul Moore wrote:
Generally, the impression I get is that the PEP is recommending more
levels of nesting than I would agree with: But it's hard to be sure,
because the concept of nesting feels a bit overloaded. The key for me
is that generally, I like to be able to
On Wed, Jun 27, 2012 at 10:57 AM, Paul Moore p.f.mo...@gmail.com wrote:
For complex stuff, subpackages
(import X.Y) might be needed, but that's rare (and even then, key
names should be exposed directly from X).
Paul.
PS Having said all this, I don't maintain any code on PyPI - I'm a
user
On Sat, Jun 23, 2012 at 3:19 AM, M Stefan mstefa...@gmail.com wrote:
* UNION_FROZENSET: like UPDATE_SET, but create a new frozenset
stack before: ... pyfrozenset mark stackslice
stack after : ... pyfrozenset.union(stackslice)
Since frozenset are immutable, could you explain how adding
If someone wants to see the error details, they should use os.stat directly
rather than an existence check.
--
Sent from my phone, thus the relative brevity :)
___
Python-Dev mailing list
Python-Dev@python.org
On 6/27/2012 3:26 PM, eric.smith wrote:
http://hg.python.org/cpython/rev/9623c83ba489
changeset: 77825:9623c83ba489
user:Eric V. Smith e...@trueblade.com
date:Wed Jun 27 15:26:26 2012 -0400
summary:
Changed importlib tests to use assertIs, assertIsInstance, etc., instead of
On 6/27/2012 4:34 PM, Terry Reedy wrote:
On 6/27/2012 3:26 PM, eric.smith wrote:
http://hg.python.org/cpython/rev/9623c83ba489
changeset: 77825:9623c83ba489
user:Eric V. Smith e...@trueblade.com
date:Wed Jun 27 15:26:26 2012 -0400
summary:
Changed importlib tests to use
20 matches
Mail list logo
