(See my posting "Let's update CObject API so it is safe and regular!"
from 2009/03/31 for "take 1").
I discussed this off-list with GvR. He was primarily concerned with
fixing the passing-around-a-vtable C API usage of CObject, but he wanted
to preserve as much backwards compatibility as po
Dirkjan Ochtman wrote:
> On 05/04/2009 20:29, "Martin v. Löwis" wrote:
>> FYI: this is the list of hooks currently employed:
>> - pre: check whitespace
>> - post: mail python-checkins
>> inform regular buildbot
>> inform community buildbot
>> trigger website rebuild if a
On Mon, Apr 6, 2009 at 10:21, Philippe Fremy wrote:
> One question: if somebody pushes a changeset with 3 commits, will the
> pre and post hooks be applied on all of the commits, or only on the
> final commit ?
>
> If this is applied on every commit, then you have no way to fix a
> whitespace prob
Daniel (ajax) Diniz wrote:
"Martin v. Löwis" wrote:
I think it would be a good idea to host a temporary svn mirrors for
developers who accesses their VCS via an IDE. Although, I am sure
anymore if supporting these developers (if there are any) would worth
the trouble. So, think of this as opt
On Mon, Apr 6, 2009 at 11:14, Philippe Fremy wrote:
> This is a problem I have with my daily usage of mercurial. It's supposed
> to be great to work offline and to commit your intermediate versions
> before it's fully working but if you do that, all those intermediate non
> working versions find t
Alex Martelli wrote:
> Queue.Queue in 2.* (and queue.Queue in 3.*) is like that too -- the
> single leading underscore meaning "protected" ("I'm here for subclasses
> to override me, only" in C++ parlance) and a great way to denote "hook
> methods" in a Template Method design pattern instance. Bas
Raymond Hettinger wrote:
Hrvoje Niksic wrote:
I've stumbled upon an oddity using sets. It's trivial to test if a
value is in the set, but it appears to be impossible to retrieve a
stored value,
See: http://code.activestate.com/recipes/499299/
Thanks, this is *really* good, the kind of id
Dirkjan Ochtman wrote:
> I have a stab at an author map at http://dirkjan.ochtman.nl/author-map.
> Could use some review, but it seems like a good start.
Martin may be able to provide a better list of names based on the
checkin name<->SSH public key mapping in the SVN setup.
(e.g. I believe my SV
Dirkjan Ochtman wrote:
> Another thing that I discussed with Georg last night would be a setup
> where changesets get pushed to a gateway repo that runs the tests and
> only pushes to an "official" repo if everything's still green. That
> should probably be a topic discussed separately, though.
Th
Nick Coghlan wrote:
Dirkjan Ochtman wrote:
Another thing that I discussed with Georg last night would be a setup
where changesets get pushed to a gateway repo that runs the tests and
only pushes to an "official" repo if everything's still green. That
should probably be a topic discussed separ
Brian Quinlan wrote:
> - you need the cooperation of your subclasses i.e. they must call
> super().flush() in .flush() to get correct close behavior (and this
> represents a backwards-incompatible semantic change)
Are you sure about that? Going by the current _pyio semantics that
Antoine poste
Alexandre Vassalotti wrote:
> On Mon, Apr 6, 2009 at 12:20 AM, Aahz wrote:
>> How difficult would it be to change the decision later? That is, how
>> about starting with a CVS-style system and maybe switch to kernel-style
>> once people get comfortable with Hg?
>
> I believe it would be fairly e
Dirkjan Ochtman wrote:
> On Mon, Apr 6, 2009 at 10:21, Philippe Fremy wrote:
>> One question: if somebody pushes a changeset with 3 commits, will the
>> pre and post hooks be applied on all of the commits, or only on the
>> final commit ?
>>
>> If this is applied on every commit, then you have no
On Mon, Apr 6, 2009 at 13:55, Michael Foord wrote:
> Gated checkins can work fine but can also have many problems. For example if
> we have a spuriously failing test then if you are working on an unrelated
> issue it will be entirely up to chance as to whether you can checkin...
Sure, it's a prob
On Sun, Apr 5, 2009 at 10:58 PM, Jack diederich wrote:
> On Sun, Apr 5, 2009 at 10:50 PM, wrote:
>> Barry> Someone asked me at Pycon about stripping out Demos and Tools.
>>
>> Matthias> +1, but please for 2.7 and 3.1 only.
>>
>> Is there a list of other demos or tools which should be delet
Martin v. Löwis wrote:
Chris Withers wrote:
Martin v. Löwis wrote:
I propose the following PEP for inclusion to Python 3.1.
Please comment.
Would this support the following case:
I have a package called mortar, which defines useful stuff:
from mortar import content, ...
I now want to dist
Benjamin Peterson wrote:
Assuming it breaks no tests, would there be objection to me committing
the
above change to the Python 3 trunk?
That's up to Benjamin. Personally, I live by "if it ain't broke, don't
fix it." :-)
Anything using an exec is broken by definition ;-)
"practicality beats pu
The 3.0 docs seem to be correct:
http://docs.python.org/3.0/tutorial/
- Forwarded message from Ernst Persson -
> Subject: Documentation site problems
> From: Ernst Persson
> To: webmas...@python.org
> Organization: StickyBit AB
> Date: Mon, 06 Apr 2009 10:32:42 +0200
>
> Hi,
>
> there
Hrm, looks like the whole 2.6 build is broken.
- Forwarded message from "M?ller-Reineke, Matthias"
-
> Subject: Library Reference is incomplete
> Date: Mon, 6 Apr 2009 11:25:54 +0200
> From: "M?ller-Reineke, Matthias"
> To: webmas...@python.org
>
> Dear Webmaster,
>
> "Library Refere
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Apr 6, 2009, at 7:55 AM, Michael Foord wrote:
Gated checkins can work fine but can also have many problems. For
example if we have a spuriously failing test then if you are working
on an unrelated issue it will be entirely up to chance as to w
Nick Coghlan writes:
> My guess was that Bazaar anchored the "centralised" end of the DVCS
> scale by letting users avoid caring about the underlying acyclic
> graph
[…]
> That makes Bazaar easy to pitch conceptually to someone like me
> ("you can use it just like you use SVN, only with much bet
On Thu, Apr 2, 2009 at 4:33 PM, M.-A. Lemburg wrote:
> On 2009-04-02 17:32, Martin v. Löwis wrote:
>> I propose the following PEP for inclusion to Python 3.1.
>
> Thanks for picking this up.
>
> I'd like to extend the proposal to Python 2.7 and later.
>
-1 to adding it to the 2.x series. There wa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Apr 6, 2009, at 9:21 AM, Jesse Noller wrote:
On Thu, Apr 2, 2009 at 4:33 PM, M.-A. Lemburg wrote:
On 2009-04-02 17:32, Martin v. Löwis wrote:
I propose the following PEP for inclusion to Python 3.1.
Thanks for picking this up.
I'd like to e
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Apr 5, 2009, at 7:37 PM, Matthias Klose wrote:
Barry Warsaw schrieb:
Someone (I'm sorry, I forgot who) asked me at Pycon about stripping
out
Demos and Tools. I'm happy to remove the two I wrote - Tools/world
and
Tools/pynche - from the dist
On Mar 29, 2009 at 05:36PM, Guido van Rossum wrote:
>> - Issue #5593: code like 1e16+2. is optimized away and its result stored
>> as
>> a constant (again), but the result can vary slightly depending on the
>> internal
>> FPU precision.
>
> I would just not bother constant folding involving
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Apr 6, 2009, at 9:21 AM, Jesse Noller wrote:
>
>> On Thu, Apr 2, 2009 at 4:33 PM, M.-A. Lemburg wrote:
>>> On 2009-04-02 17:32, Martin v. Löwis wrote:
I propose the following PEP for inclusion to Python 3.1.
>>>
>>> Thanks for picking t
Cesare Di Mauro a-tono.com> writes:
> def f(): return ['a', ('b', 'c')] * (1 + 2 * 3)
[...]
>
> With proper constant folding code, both functions can be reduced
> to a single LOAD_CONST and a RETURN_VALUE (or, definitely, by
> a single instruction at all with an advanced peephole optimizer).
Lis
At 02:00 PM 4/6/2009 +0100, Chris Withers wrote:
Martin v. Löwis wrote:
Chris Withers wrote:
Would this support the following case:
I have a package called mortar, which defines useful stuff:
from mortar import content, ...
I now want to distribute large optional chunks separately, but ideal
P.J. Eby wrote:
See the third paragraph of
http://www.python.org/dev/peps/pep-0382/#discussion
Indeed, I guess the PEP could be made more explanatory then 'cos, as a
packager, I don't see what I'd put in the various setup.py and
__init__.py to make this work...
That said, I'm delighted to
On Mon, Apr 6, 2009 at 9:26 AM, Barry Warsaw wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Apr 6, 2009, at 9:21 AM, Jesse Noller wrote:
>
>> On Thu, Apr 2, 2009 at 4:33 PM, M.-A. Lemburg wrote:
>>>
>>> On 2009-04-02 17:32, Martin v. Löwis wrote:
I propose the following
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brett Cannon wrote:
> During the PyCon sprint I tried to make BaseException accept only a single
> argument and bind it to BaseException.message . I was successful (see the
> p3yk_no_args_on_exc branch), but it was very painful to pull off as anyone
>
On Mon, 6 Apr 2009 at 12:00, Jesse Noller wrote:
On Mon, Apr 6, 2009 at 9:26 AM, Barry Warsaw wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Apr 6, 2009, at 9:21 AM, Jesse Noller wrote:
On Thu, Apr 2, 2009 at 4:33 PM, M.-A. Lemburg wrote:
On 2009-04-02 17:32, Martin v. L?wis wrot
On Mon, Apr 6, 2009 at 12:28 PM, R. David Murray wrote:
> On Mon, 6 Apr 2009 at 12:00, Jesse Noller wrote:
>>
>> On Mon, Apr 6, 2009 at 9:26 AM, Barry Warsaw wrote:
>>>
>>> -BEGIN PGP SIGNED MESSAGE-
>>> Hash: SHA1
>>>
>>> On Apr 6, 2009, at 9:21 AM, Jesse Noller wrote:
>>>
On Thu, A
Cesare> At this time with Python 2.6.1 we have these results:
Cesare> def f(): return 1 + 2 * 3 + 4j
...
Cesare> def f(): return ['a', ('b', 'c')] * (1 + 2 * 3)
Guido can certainly correct me if I'm wrong, but I believe the main point of
his message was that you aren't going to en
On Lun, Apr 6, 2009 16:43, Antoine Pitrou wrote:
> Cesare Di Mauro a-tono.com> writes:
>> def f(): return ['a', ('b', 'c')] * (1 + 2 * 3)
> [...]
>>
>> With proper constant folding code, both functions can be reduced
>> to a single LOAD_CONST and a RETURN_VALUE (or, definitely, by
>> a single inst
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jesse Noller wrote:
> On Mon, Apr 6, 2009 at 12:28 PM, R. David Murray
> wrote:
>> On Mon, 6 Apr 2009 at 12:00, Jesse Noller wrote:
>>> On Mon, Apr 6, 2009 at 9:26 AM, Barry Warsaw wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nick Coghlan wrote:
Brian Quinlan wrote:
- you need the cooperation of your subclasses i.e. they must call
super().flush() in .flush() to get correct close behavior (and this
represents a backwards-incompatible semantic change)
Are you sure about that? Going by the current _pyio semantics
On Mon, Apr 6, 2009 18:57, s...@pobox.com wrote:
>
> Cesare> At this time with Python 2.6.1 we have these results:
> Cesare> def f(): return 1 + 2 * 3 + 4j
> ...
> Cesare> def f(): return ['a', ('b', 'c')] * (1 + 2 * 3)
>
> Guido can certainly correct me if I'm wrong, but I believe
[Antoine]
> - Issue #5593: code like 1e16+2. is optimized away and its result stored
> as
> a constant (again), but the result can vary slightly depending on the internal
> FPU precision.
[Guido]
> I would just not bother constant folding involving FP, or only if the
> values involved have an
+1 for removing constant folding for floats (besides conversion
of -). There are just too many things to worry about:
FPU rounding mode and precision, floating-point signals and flags,
effect of compiler flags, and the potential benefit seems small.
If you're talking about the existing peepho
Hi,
On Sun, Mar 29, 2009 at 10:21 AM, Jeffrey Yasskin wrote:
> I've heard some good things about cmake — LLVM, googletest, and Boost
> are all looking at switching to it — so I wanted to see if we could
> simplify our autoconf+makefile system by using it. The biggest wins I
> see from going to cm
On Mon, Apr 6, 2009 at 9:05 PM, Raymond Hettinger wrote:
> The code for the lsum() recipe is more readable with a line like:
>
> exp = long(mant * 2.0 ** 53)
>
> than with
>
> exp = long(mant * 9007199254740992.0)
>
> It would be ashamed if code written like the former suddenly
> started doing t
I committed some new telnetlib tests yesterday to the trunk and I can
see they are failing on Neal's setup but not what the failures are.
Ideally I like to get the information out of the buildbots but they
all seem to be hanging on stdio tests and quiting out.
Ideas? TIA,
-Jack
_
Jack diederich gmail.com> writes:
>
> I committed some new telnetlib tests yesterday to the trunk and I can
> see they are failing on Neal's setup but not what the failures are.
> Ideally I like to get the information out of the buildbots but they
> all seem to be hanging on stdio tests and quiti
On Mon, Apr 6, 2009 at 7:28 AM, Cesare Di Mauro
wrote:
> The Language Reference says nothing about the effects of code optimizations.
> I think it's a very good thing, because we can do some work here with constant
> folding.
Unfortunately the language reference is not the only thing we have to
w
On Mon, Apr 6, 2009 at 1:22 PM, Mark Dickinson wrote:
> On Mon, Apr 6, 2009 at 9:05 PM, Raymond Hettinger wrote:
>> The code for the lsum() recipe is more readable with a line like:
>>
>> exp = long(mant * 2.0 ** 53)
>>
>> than with
>>
>> exp = long(mant * 9007199254740992.0)
>>
>> It would be
Anyone able to look into this and fix it? Having all of the normal
entrypoints for documentation broken is rather inconvenient for users :-)
On Mon, Apr 6, 2009 at 15:06, Aahz wrote:
> Hrm, looks like the whole 2.6 build is broken.
>
> - Forwarded message from "M?ller-Reineke, Matthias" <
>
Tres Seaver wrote:
> I don't think either of these classes should be subject to a deprecation
> warning for a feature they never used or depended on.
Agreed. Could you raise a tracker issue for the spurious warnings? (I
believe we should be able to make the warning condition a bit smarter to
elimi
Ben Finney wrote:
> Nick Coghlan writes:
>> Mercurial appears to best allow the sales pitch to be tailored to
>> the target audience (in this case, a group including a lot of people
>> with a background predominantly involving centralised version
>> control tools).
>
> I don't follow. Wouldn't yo
Nick Coghlan wrote:
> Dirkjan Ochtman wrote:
>> I have a stab at an author map at http://dirkjan.ochtman.nl/author-map.
>> Could use some review, but it seems like a good start.
>
> Martin may be able to provide a better list of names based on the
> checkin name<->SSH public key mapping in the SVN
On Mon, Apr 6, 2009 at 2:22 PM, Mark Dickinson wrote:
> Well, I'd say that the obvious solution here is to compute
> the constant 2.0**53 just once, somewhere outside the
> inner loop. In any case, that value would probably be better
> written as 2.0**DBL_MANT_DIG (or something similar).
>
> As A
> You can commit some temporary debug output in the tests (just sprinkle those
> print()'s you need to get your tasty information).
Also, if you want to do a sequence of changes to test a specific
machine, you might want to create a branch, make those changes, and then
trigger a build of that bran
there contents is missing from the python tutorial:
The 3.0 docs seem to be correct:
http://docs.python.org/3.0/tutorial/
It seems it is not the case anymore. The devel doc from Python 3 are
missing a few tables of contents as well:
http://docs.python.org/dev/py3k/tutorial/
When I build the
On Tue, 7 Apr 2009 07:27:29 am Guido van Rossum wrote:
> Unfortunately the language reference is not the only thing we have to
> worry about. Unlike languages like C++, where compiler writers have
> the moral right to modify the compiler as long as they stay within
> the weasel-words of the standa
On Mon, Apr 6, 2009 at 5:10 PM, Steven D'Aprano wrote:
> On Tue, 7 Apr 2009 07:27:29 am Guido van Rossum wrote:
>
>> Unfortunately the language reference is not the only thing we have to
>> worry about. Unlike languages like C++, where compiler writers have
>> the moral right to modify the compile
David Cournapeau wrote:
> On Mon, Mar 30, 2009 at 2:59 AM, Antoine Pitrou
> wrote:
...
>
> Waf is definitely faster than scons - something like one order of
> magnitude. I am yet very familiar with waf, but I like what I saw -
> the architecture is much nicer than scons (waf core amount of code
Ondrej Certik wrote:
> Hi,
>
> On Sun, Mar 29, 2009 at 10:21 AM, Jeffrey Yasskin wrote:
>> I've heard some good things about cmake — LLVM, googletest, and Boost
>> are all looking at switching to it — so I wanted to see if we could
>> simplify our autoconf+makefile system by using it. The biggest
Dirkjan Ochtman wrote:
> On Mon, Apr 6, 2009 at 06:20, Alexandre Vassalotti
> wrote:
>> But that won't work if people who are not core developers submit us
>> patch bundle to import. And maintaining a such white-list sounds to me
>> more burdensome than necessary.
>
> Well, if you need contributo
Hi,
I'm trying to write a C extension which is a subclass of dict.
I want to do something like a setdefault() but with a single lookup.
Looking through the dictobject code, the three workhorse
routines lookdict, insertdict and dictresize are not available
directly for functions outside dictobject
Steve Holden wrote:
Isn't it strange how nobody every complained about the significance of
whitespace in makefiles: only the fact that leading tabs were required
rather than just-any-old whitespace.
Make doesn't care how *much* whitespace there
is, though, only whether it's there or not. If
it
The decorator module [1] written by Michele Simionato is a very useful
tool for maintaining function signatures while applying a decorator.
Many different projects implement their own versions of the same
functionality, for example turbogears has its own utility for this, I
guess others do somethin
Alexandre Vassalotti writes:
> This makes me remember that we will have to decide how we will
> reorganize our workflow. For this, we can either be conservative and
> keep the current CVS-style development workflow--i.e., a few main
> repositories where all developers can commit to.
That was
On Tue, Apr 7, 2009 at 00:05, "Martin v. Löwis" wrote:
> I think the identification in the SSH keys is useless. It contains
> strings like "loe...@mira" or "ncogh...@uberwald", or even multiple
> of them (ba...@wooz, ba...@resist, ...).
Right, so we'll put up the author map somewhere with the ema
On Tue, Apr 7, 2009 at 2:03 AM, Stephen J. Turnbull wrote:
> Alexandre Vassalotti writes:
>
> > This makes me remember that we will have to decide how we will
> > reorganize our workflow. For this, we can either be conservative and
> > keep the current CVS-style development workflow--i.e., a fe
On Tue, Apr 7, 2009 at 04:25, Steve Holden wrote:
> I would remind you all that it's *very* necessary to make sure that
> whatever finds its way into released code is indeed covered by
> contributor agreements. The PSF (as the guardian of the IP) has to
> ensure this, and so we have to find a way
Dirkjan Ochtman writes:
> Right. It's basically "Name Lastname " -- we can verify that
> in a hook.
Remembering, of course, that full names don't follow any template
(especially not first-name last-name). The person's full name must be
treated as free-form text, since there's no format common to
On Tue, Apr 7, 2009 at 08:25, Ben Finney wrote:
> Remembering, of course, that full names don't follow any template
> (especially not first-name last-name). The person's full name must be
> treated as free-form text, since there's no format common to all.
Of course, unless we lock it down through
67 matches
Mail list logo
