Hi all,
For the past two days I've been doing some housekeeping
*cough*spamming*cough* on the tracker, mostly on ancient and/or easy
bugs. So far, ten bugs have been closed (thanks Antoine, Barry,
Benjamin, Guilherme, Martin and Raymond). I nominated some other bugs
(below) for closing and added
2009/2/10 Daniel (ajax) Diniz aja...@gmail.com:
If anyone is interested in being added as nosy for any category of
bugs, let me know and I'll do that as I scan the tracker.
Anything related to Decimal, add me.
Thanks!
--
.Facundo
Blog: http://www.taniquetil.com.ar/plog/
PyAr:
Thanks Daniel! This kind of work is never fun but very much needed and
I'm very glad you did it. A round of applause!!
On Tue, Feb 10, 2009 at 5:23 AM, Daniel (ajax) Diniz aja...@gmail.com wrote:
Hi all,
For the past two days I've been doing some housekeeping
*cough*spamming*cough* on the
In peephole.c I noticed some expression optimizations:
/* not a is b -- a is not b
not a in b -- a not in b
not a is not b -- a is b
not a not in b -- a in
On Tue, Feb 10, 2009 at 10:24 AM, Cesare Di Mauro cesare.dima...@a-tono.com
wrote:
Could it be applyable to other operations as well? So, if I wrote:
c = not(a b)
the compiler and/or peephole optimizer can generate bytecodes instructions
which, instead, execute the following operation:
c
Cesare Di Mauro cesare.dimauro at a-tono.com writes:
Could it be applyable to other operations as well? So, if I wrote:
c = not(a b)
the compiler and/or peephole optimizer can generate bytecodes instructions
which, instead, execute the
following operation:
c = a = b
Is it right?
Daniel Stutzbach wrote:
On Tue, Feb 10, 2009 at 10:24 AM, Cesare Di Mauro
cesare.dima...@a-tono.com mailto:cesare.dima...@a-tono.com wrote:
Could it be applyable to other operations as well? So, if I wrote:
c = not(a b)
the compiler and/or peephole optimizer can generate
On Tue, Feb 10, 2009 at 11:16 AM, Steve Holden st...@holdenweb.com wrote:
That's true, but the same *could* be said about the existing
optimizations for objects that define their own __contains__.
No, because there isn't a __not_contains__, so you cannot define the inverse
operation
Steve Holden steve at holdenweb.com writes:
That's true, but the same *could* be said about the existing
optimizations for objects that define their own __contains__.
No, because there is no such thing as __not_contains__.
Regards
Antoine.
___
On Tue, Feb 10, 2009 at 05:23, Daniel (ajax) Diniz aja...@gmail.com wrote:
Hi all,
For the past two days I've been doing some housekeeping
*cough*spamming*cough* on the tracker, mostly on ancient and/or easy
bugs. So far, ten bugs have been closed (thanks Antoine, Barry,
Benjamin,
- Original Message -
From: Cesare Di Mauro cesare.dima...@a-tono.com
To: Python-Dev python-dev@python.org
Sent: Tuesday, February 10, 2009 8:24 AM
Subject: [Python-Dev] Expression optimizations
In peephole.c I noticed some expression optimizations:
/* not a is b -- a is not b
On Tue, Feb 10, 2009 at 8:23 AM, Daniel (ajax) Diniz aja...@gmail.com wrote:
If anyone is interested in being added as nosy for any category of
bugs, let me know and I'll do that as I scan the tracker.
Adding/assigning to me on 2to3 bugs is fine, but usually I notice
stuff I'm interested in as
On Mar, Feb 10, 2009 at 05:38 PM, Daniel Stutzbach wrote:
On Tue, Feb 10, 2009 at 10:24 AM, Cesare Di Mauro
cesare.dima...@a-tono.com
wrote:
Could it be applyable to other operations as well? So, if I wrote:
c = not(a b)
the compiler and/or peephole optimizer can generate bytecodes
On Tue, Feb 10, 2009 at 2:36 PM, Cesare Di Mauro
cesare.dima...@a-tono.comwrote:
OK, so I can make assumptions only for built-in types.
Yes, but even there you have to be careful of odd corner-cases, such as:
nan = float('nan')
nan nan
False
nan = nan
False
--
Daniel Stutzbach, Ph.D.
On Mar, Feb 10, 2009 06:24 PM, Daniel Stutzbach wrote:
On Tue, Feb 10, 2009 at 11:16 AM, Steve Holden st...@holdenweb.com
wrote:
That's true, but the same *could* be said about the existing
optimizations for objects that define their own __contains__.
No, because there isn't a
On Mar, Feb 10, 2009 08:15 PM, Raymond Hettinger wrote:
- Original Message -
From: Cesare Di Mauro cesare.dima...@a-tono.com
To: Python-Dev python-dev@python.org
Sent: Tuesday, February 10, 2009 8:24 AM
Subject: [Python-Dev] Expression optimizations
In peephole.c I noticed some
On Mar, Feb 10, 2009 09:42PM, Daniel Stutzbach wrote:
On Tue, Feb 10, 2009 at 2:36 PM, Cesare Di Mauro
cesare.dima...@a-tono.comwrote:
OK, so I can make assumptions only for built-in types.
Yes, but even there you have to be careful of odd corner-cases, such as:
nan = float('nan')
nan
And slightly unrelated, but just showing how bizarre floats are:
x = 1e6
y = x/x
cmp(y, y)
0
cmp(x/x, x/x)
-1
Yeah object identity checks!
From: python-dev-bounces+dinov=microsoft@python.org
[mailto:python-dev-bounces+dinov=microsoft@python.org] On Behalf Of Daniel
Stutzbach
It's bizarre enough, since I have got a different result (with Python
2.6.1, 32 bit):
x = 1e6
y = x/x
x
inf
y
nan
cmp(y, y)
0
cmp(x/x, x/x)
1
:D
Cesare
On Mar, Feb 10, 2009 10:02PM, Dino Viehland wrote:
And slightly unrelated, but just showing how bizarre floats are:
x = 1e6
I think it's comparing based upon object identity so it may be a little
non-deterministic:
x= 1e66
y = x/x
z = x/x
cmp(y, z)
1
cmp(z, y)
-1
But I may have accidently run that on IronPython though where we're assigning
ids differently :)
-Original Message-
From: Cesare Di
[Cesare Di Mauro]
I'm playing with the virtual machine and I have some ideas about possibile
optimizations that could be applyed. But I need to verify them, so
understanding what is possible and what is not, is a primary goal for me.
The best way to understand what is possible is to
On Tue, Feb 10, 2009 at 05:23, Daniel (ajax) Diniz aja...@gmail.com wrote:
[SNIP]
Iff this kind of Bug-Day-ish work is desirable, doesn't disrupt real
work and people agree the workflow would be better, I'd like to have
developer rights in the tracker, as per Antoine's suggestion. FWIW, I
On Tue, Feb 10, 2009 at 2:23 PM, Daniel (ajax) Diniz aja...@gmail.com wrote:
If anyone is interested in being added as nosy for any category of
bugs, let me know and I'll do that as I scan the tracker.
I'll take Distutils related issues,
Thank you
Tarek
On Mar, Feb 10, 2009 10:20PM, Raymond Hettinger wrote:
[Cesare Di Mauro]
I'm playing with the virtual machine and I have some ideas about
possibile
optimizations that could be applyed. But I need to verify them, so
understanding what is possible and what is not, is a primary goal for
me.
Brett Cannon wrote:
OK, three enthusiastic votes to give them is plenty for me. You should have
the Developer role now, Daniel. Let me know if I screwed up at all in
switchng the role on for you.
Thanks a lot! Looks like it worked fine :)
Let me try the new thing, then: warnings and import
On 2009-02-10, Tarek Ziadé wrote:
On Tue, Feb 10, 2009 at 2:23 PM, Daniel (ajax) Diniz aja...@gmail.com wrote:
If anyone is interested in being added as nosy for any category of
bugs, let me know and I'll do that as I scan the tracker.
I'll take Distutils related issues,
If you could
Dear Python developers,
Introduction:
I am writing from the perspective of Sugar Labs [1], which produces Sugar, a
free software project written almost entirely in Python. Sugar is designed
to run on small, resource-constrained computers. So far those computers
have been mostly x86, but it
On Tue, Feb 10, 2009 at 18:45, Benjamin Schwartz
bmsch...@fas.harvard.eduwrote:
Dear Python developers,
Introduction:
I am writing from the perspective of Sugar Labs [1], which produces Sugar,
a
free software project written almost entirely in Python. Sugar is designed
to run on small,
Brett Cannon wrote:
On Tue, Feb 10, 2009 at 18:45, Benjamin Schwartz
bmsch...@fas.harvard.eduwrote:
...
According to ARM [4]:
Jazelle RCT can be used to significantly reduce the code bloat
associated
with AOT and JIT compilation, making AOT technology viable on mass-market
devices. It
ISTM, that when closing duplicate bug reports, both should reference one
another so that the combined threads don't get lost.
Also, assigning bugs to people who haven't asked to handle them doesn't seem like it is actually cleaning-up anything. If something
is assigned to someone, I usually
On Tue, Feb 10, 2009 at 8:57 PM, Raymond Hettinger pyt...@rcn.com wrote:
ISTM, that when closing duplicate bug reports, both should reference one
another so that the combined threads don't get lost.
This suggest a feature request (which Google's internal tracker has):
when a bug is closed as
I ran 2.6, 3.0, and 3.1 manually. 2.7 should get picked up on the
next run. The problem is that regrtest.py -R hangs from time to time
which caused the machine to run out of memory. Does anyone else have
regrtest.py -R hang for them? Some tests were disabled to try to
prevent the problem, but
Hi Raymond,
Thanks a lot for the feedback. I actually am more than a bit concerned
about the effect of my wholesale edits on the signal to noise ration.
Any clarifications are most welcome (and I'm open to change methods
and immediate goals) :)
Raymond Hettinger wrote:
ISTM, that when closing
Brett Cannon wrote:
Warnings and import for me.
Done. Tomorrow I'll see what I can triage/test in those.
Talking about Bug Days, I see lots of easy bugs, some with outdated
patches. Is there any plan of doing a Bug Day around PyCon time?
Well, the sprints at PyCon are Bug Days themselves
Tarek Ziadé wrote:
I'll take Distutils related issues,
Done. Since Akira Kitada is helping with many distutils issues, I'll
skip looking at them for now. Ping me if you need tests or simple
patches :)
Regards,
Daniel
___
Python-Dev mailing list
Benjamin Peterson wrote:
Adding/assigning to me on 2to3 bugs is fine, but usually I notice
stuff I'm interested in as it rises to the top.
Done, found a couple more. There are also some -3 warnings open, if
that interests you :)
Thanks for the support, I only saw it was a +10 now :D
Cheers,
ARM is specifically claiming that these instructions can be used to
accelerate Python interpretation.
Wow, really? One of the links below mention that?
I'm skeptical though that you can really produce speedups for CPython,
though; ISTM that they added Python only as a front-end
- fast instance variables: likewise, with R10 holding the this
pointer. Not applicable to Python, since there is no byte code
for instance variable access.
Follow-up: this could be used to JIT LOAD_CONST efficiently, though,
putting co_consts into R10.
Regards,
Martin
38 matches
Mail list logo
