Hi,
Georg Brandl gmx.net> writes:
>
> I would argue that the __enter__ and __exit__ behavior should be changed too.
> The reason for the current behavior is this:
>
[...]
>
> IOW, when "with" is compiled, the attributes are retrieved using bytecode.
> It wouldn't be hard to have a WITH_SETUP
Georg Brandl wrote:
Nick Coghlan schrieb:
2. Method lookup MAY bypass __getattribute__, shadowing the attribute
in the instance dictionary MAY have ill effects. (slots such as
__enter__ and __exit__ that are looked up via normal attribute lookup
in CPython will fit into this category)
I wou
M.-A. Lemburg wrote:
On 2008-06-12 16:59, Walter Dörwald wrote:
M.-A. Lemburg wrote:
.transform() and .untransform() use the codecs to apply same-type
conversions. They do apply type checks to make sure that the
codec does indeed return the same type.
E.g. text.transform('xml-escape') or data.
Nick Coghlan gmail.com> writes:
> That said, the with statement implementation is already a bit different
> in 2.6/3.0 (it moves things around on the stack so it can avoid the
> STORE_FAST/LOAD_FAST/DELETE_FAST operations):
Hmm, check again with the current 3.0 - it has changed back to storing
On 2008-06-13 11:32, Walter Dörwald wrote:
M.-A. Lemburg wrote:
On 2008-06-12 16:59, Walter Dörwald wrote:
M.-A. Lemburg wrote:
.transform() and .untransform() use the codecs to apply same-type
conversions. They do apply type checks to make sure that the
codec does indeed return the same type.
Guido van Rossum wrote:
It's water under the bridge now, but IMO it was too rash to *remove*
the old threading API from Py3k, and doubly rash to do so one day
before the beta release. Running up to a release (whether alpha, beta
or final) we should practice extra restraint, not rush to get things
Guido van Rossum wrote:
[Barry]
http://bugs.python.org/issue643841
[Guido]
I've added a comment. Let me know if anything I said is unclear.
On Thu, Jun 12, 2008 at 3:35 AM, Nick Coghlan <[EMAIL PROTECTED]> wrote:
The bugtracker seems to be offline atm - I'll reply
Guido van Rossum wrote:
[Barry]
http://bugs.python.org/issue643841
[Guido]
I've added a comment. Let me know if anything I said is unclear.
On Thu, Jun 12, 2008 at 3:35 AM, Nick Coghlan <[EMAIL PROTECTED]> wrote:
The bugtracker seems to be offline atm - I'll reply
On Tuesday 10 June 2008 08:16:26 Martin v. Löwis wrote:
> I just finished a PEP 3121 implementation, uploaded at
>
> http://codereview.appspot.com/1962
In the patch to 'Python/import.c' there is a comment line '
+ Modules which do support multiple multiple initialization set
+ their m_size fie
Steve Holden wrote:
Guido van Rossum wrote:
It's water under the bridge now, but IMO it was too rash to *remove*
the old threading API from Py3k, and doubly rash to do so one day
before the beta release. Running up to a release (whether alpha, beta
or final) we should practice extra restraint, n
Antoine Pitrou schrieb:
Hi,
Georg Brandl gmx.net> writes:
I would argue that the __enter__ and __exit__ behavior should be changed too.
The reason for the current behavior is this:
[...]
IOW, when "with" is compiled, the attributes are retrieved using bytecode.
It wouldn't be hard to have
M.-A. Lemburg wrote:
On 2008-06-13 11:32, Walter Dörwald wrote:
M.-A. Lemburg wrote:
On 2008-06-12 16:59, Walter Dörwald wrote:
M.-A. Lemburg wrote:
.transform() and .untransform() use the codecs to apply same-type
conversions. They do apply type checks to make sure that the
codec does indeed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It's unfortunate that I was not able to release the first betas on
Wednesday. The primary reason was that none of the 3.0 buildbots were
green.
My proposal is this: I will spin another release this coming
Wednesday, June 18. If we can get bo
2008/6/13 Barry Warsaw <[EMAIL PROTECTED]>:
> My proposal is this: I will spin another release this coming Wednesday, June
> 18. If we can get both the 2.6 and 3.0 buildbots green by then, and close
> out all remaining release critical bugs, then Wednesday's release will be
> beta 1. In that cas
On Fri, Jun 13, 2008 at 6:54 AM, Facundo Batista
<[EMAIL PROTECTED]> wrote:
> 2008/6/13 Barry Warsaw <[EMAIL PROTECTED]>:
>
>> My proposal is this: I will spin another release this coming Wednesday, June
>> 18. If we can get both the 2.6 and 3.0 buildbots green by then, and close
>> out all remain
Guido van Rossum schrieb:
On Fri, Jun 13, 2008 at 6:54 AM, Facundo Batista
<[EMAIL PROTECTED]> wrote:
2008/6/13 Barry Warsaw <[EMAIL PROTECTED]>:
My proposal is this: I will spin another release this coming Wednesday, June
18. If we can get both the 2.6 and 3.0 buildbots green by then, and cl
On Fri, Jun 13, 2008 at 7:27 AM, Georg Brandl <[EMAIL PROTECTED]> wrote:
> Guido van Rossum schrieb:
>>
>> On Fri, Jun 13, 2008 at 6:54 AM, Facundo Batista
>> <[EMAIL PROTECTED]> wrote:
>>>
>>> 2008/6/13 Barry Warsaw <[EMAIL PROTECTED]>:
>>>
My proposal is this: I will spin another release thi
On Fri, Jun 13, 2008 at 9:20 AM, Guido van Rossum <[EMAIL PROTECTED]> wrote:
>
> I'm fine with whatever delay Barry approves, but I want EVERYONE to
> stick to the purpose of the delay: get the buildbots green and close
> out release critical bugs. This means no new last-minute features or
> big re
Hello guys,
/* Helper for passing objects to printf and the like */
#define PyObject_REPR(obj) PyUnicode_AsString(PyObject_Repr(obj))
3k might be a good moment to kill that leak-suggesting macro.
--
Gustavo Niemeyer
http://niemeyer.net
___
Python
Walter Dörwald wrote:
[...]
Sure, we could do that, but please use a different name,
e.g. .encodeall() and .decodeall() - .encode() and .decode()
are already stateles (and so would the new methods be), so
"stateless" isn't all that meaningful in this context.
I like the names encodeall/decode
On Fri, Jun 13, 2008 at 6:07 AM, Nick Coghlan <[EMAIL PROTECTED]> wrote:
> Steve Holden wrote:
>>
>> Guido van Rossum wrote:
>>>
>>> It's water under the bridge now, but IMO it was too rash to *remove*
>>> the old threading API from Py3k, and doubly rash to do so one day
>>> before the beta release
On Thu, Jun 12, 2008 at 11:32 PM, Georg Brandl <[EMAIL PROTECTED]> wrote:
> Guido van Rossum schrieb:
>>
>> It's water under the bridge now, but IMO it was too rash to *remove*
>> the old threading API from Py3k, and doubly rash to do so one day
>> before the beta release. Running up to a release (
Guido van Rossum schrieb:
On Thu, Jun 12, 2008 at 11:32 PM, Georg Brandl <[EMAIL PROTECTED]> wrote:
Guido van Rossum schrieb:
It's water under the bridge now, but IMO it was too rash to *remove*
the old threading API from Py3k, and doubly rash to do so one day
before the beta release. Running
Hello,
In the true spirit of the anti-code retention meme launched by Guido, I've
posted a patch implementing the implicit exception chaining part of PEP 3134.
The core functionality is there, but its consequences on exception reporting
are still non-existent (no funky multi-traceback exception m
On Fri, Jun 13, 2008 at 6:14 PM, Antoine Pitrou <[EMAIL PROTECTED]> wrote:
>
> Hello,
>
> In the true spirit of the anti-code retention meme launched by Guido, I've
> posted a patch implementing the implicit exception chaining part of PEP 3134.
> The core functionality is there, but its consequence
25 matches
Mail list logo
