Hi,
I guess it would be a good idea to quickly outline my inline caching
approach, so that we all have a basic understanding of how it works.
If we take for instance the BINARY_ADD instruction, the interpreter
evaluates the actual operand types and chooses the matching operation
implementation at
On Thu, Jul 22, 2010 at 6:50 PM, Eric Smith wrote:
> Thanks for writing this, Tim.
>
> On 7/21/10 11:11 AM, Tim Golden wrote:
>
>> The issue of a __format__ equivalent for bytes was also raised as was the
>> idea of object methods to render an object as string or bytes, which could
>> be used in t
Hi,
stefan brunthaler, 22.07.2010 13:22:
during the last year, I have developed a couple of quickening-based
optimizations for the Python 3.1 interpreter. As part of my PhD
programme, I have published a first technique that combines quickening
with inline caching at this year's ECOOP, and subseq
Sorry, this should have gone to cython-dev, not python-dev ...
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.co
Hi,
Stefan Brunthaler started a thread on python-dev about a couple of patches
he has written for CPython as part of his PhD. It seems that he has
implemented inline caching for CPython.
http://comments.gmane.org/gmane.comp.python.devel/115362
http://en.wikipedia.org/wiki/Inline_caching
Som
Georg Brandl, 22.07.2010 16:13:
Am 22.07.2010 13:29, schrieb Antoine Pitrou:
Le jeudi 22 juillet 2010 à 07:23 -0500, Benjamin Peterson a écrit :
2010/7/22 Antoine Pitrou:
Brett Cannon wrote:
Basically the whole setting a module's globals to None was done before gc
came into the language. Now
Maciej Fijalkowski, 22.07.2010 10:43:
On Thu, Jul 22, 2010 at 9:51 AM, Brett Cannon wrote:
Basically the whole setting a module's globals to None was done before gc
came into the language. Now that it's there it seems that it might work to
simply let gc clean up the module itself. But this bring
On Fri, 23 Jul 2010 10:59:32 am Ben Finney wrote:
> Steven D'Aprano writes:
> > We don't need to make excuses for why we don't give the answer
> > here. It's enough to give the reason -- it's off-topic for this
> > list, which is about the development of Python. That and a pointer
> > to the right
Georg Brandl wrote:
> Am 22.07.2010 13:29, schrieb Antoine Pitrou:
>> Is it the reason why? With the new module creation API in 3.x, extension
>> modules should be able to handle deletion of their own internal
>> resources.
>
> Yes, but as Martin noted at the summit, nobody since went through all
On 23/07/10 04:24, gregory.smi...@sympatico.ca wrote:
I've suggested :name, which doesn't break old code,
I'm not so sure about that. Consider
foo[a::b]
Do you parse that as a 3-element slice, or as a
2-element slice with :b as the second element?
--
Greg
Steven D'Aprano writes:
> We don't need to make excuses for why we don't give the answer here.
> It's enough to give the reason -- it's off-topic for this list, which
> is about the development of Python. That and a pointer to the right
> list is, in my opinion, all we need to say. We don't need
Am 22.07.2010 21:49, schrieb Reid Kleckner:
> On Thu, Jul 22, 2010 at 11:49 AM, Alexander Belopolsky
> wrote:
>> On Thu, Jul 22, 2010 at 12:53 PM, wrote:
>>> I'm very amused by all the jokes about turning python into perl, but there's
>>> a good idea here that doesn't actually require that...
>>
On 22/07/2010 23:25, Terry Reedy wrote:
On 7/22/2010 8:22 AM, Steven D'Aprano wrote:
On Thu, 22 Jul 2010 07:02:33 pm Stephen J. Turnbull wrote:
OTOH I think as quick as possible an answer is a good idea here. It
saves the intended audience the thought about whether to reply or
not, and an inst
On Fri, Jul 23, 2010 at 3:30 AM, Alexander Belopolsky
wrote:
> I see three solutions:
>
> 1. Minimal: do not rename test_trace in 2.7 and add trace module
> tests to the existing file. Whether to revert test_trace to
> test_line_tracing renaming in 3.2 can be decided after we have 2.7
> tests w
On Fri, Jul 23, 2010 at 2:25 AM, Alexander Belopolsky
wrote:
> Note also that argparse/optparse does not know about -m way either:
>
> $ python -m profile -h
> Usage: profile.py [-o output_file_path] [-s sort] scriptfile [arg] ...
>
> I am not sure if it is possible for argparse to distinguish bet
On 7/22/2010 8:22 AM, Steven D'Aprano wrote:
On Thu, 22 Jul 2010 07:02:33 pm Stephen J. Turnbull wrote:
OTOH I think as quick as possible an answer is a good idea here. It
saves the intended audience the thought about whether to reply or
not, and an instant, constructive answer says that someb
On Fri, Jul 23, 2010 at 12:42 AM, Georg Brandl wrote:
> Sure -- I don't think this is a showstopper for regex. However if we don't
> include regex in a future version, we might think about increasing MAXCACHE
> a bit, and maybe not clear the cache when it reaches its max length, but
> rather remo
> Date: Thu, 22 Jul 2010 14:49:17 -0400
> Subject: Re: [Python-Dev] Set the namespace free!
> From: alexander.belopol...@gmail.com
> To: gregory.smi...@sympatico.ca
> CC: python-dev@python.org
>
> On Thu, Jul 22, 2010 at 12:53 PM, wrote:
> ..
> > So, ::name or &name or |name or whatever.
> >
On 7/22/2010 3:29 PM, average wrote:
Speacking of etiquette, it is traditional to use real names in the from
field on pydev. It will get you more attention and respect.
A reference or link to ESR's "How to Ask Questions The Smart Way"
(http://catb.org/esr/faqs/smart-questions.html) is a prett
On 7/22/2010 2:04 PM, John Nagle wrote:
From: Bartosz Tarnowski
Python has more and more reserved words over time
...
What should I do then, when the attribute is a reserver word?
I am going to be a grinch and note that this is strictly a usage
question with no development implications.
On 7/22/2010 9:36 AM, stefan brunthaler wrote:
Depending on the size and complexity of the
patches, it may still be worth exploring for 3.2.
If your work speeds CPython, U.S. would have to be even better to knock
it out.
I am currently not aware of the planned release schedule, but I think
On Thu, Jul 22, 2010 at 11:49 AM, Alexander Belopolsky
wrote:
> On Thu, Jul 22, 2010 at 12:53 PM, wrote:
>> I'm very amused by all the jokes about turning python into perl, but there's
>> a good idea here that doesn't actually require that...
>
> No, there isn't. And both '&' and '|' are valid
> > > ...After a sufficient period of waiting, say a day or two with no
> response:
> >
> > Ok, I'll wait a bit longer.
>
> I don't think that's a good idea.
My bad, I really only meant a "sufficient delay to allow the
possibility of an interested party replying". I actually figured
about
> Using "setattr" to set attributes, where the attribute string
> comes from an external source, can create a security hole. Remember
> that you can override functions on an object, for that object only,
> by setting an attribute. This offers the opportunity for an attack
> similar to SQL in
> Using "setattr" to set attributes, where the attribute string
> comes from an external source, can create a security hole. Remember
> that you can override functions on an object, for that object only,
> by setting an attribute. This offers the opportunity for an attack
> similar to SQL in
On Thu, Jul 22, 2010 at 12:53 PM, wrote:
..
> So, ::name or &name or |name or whatever.
>
> I'm very amused by all the jokes about turning python into perl, but there's
> a good idea here that doesn't actually require that...
No, there isn't. And both '&' and '|' are valid python operators that
I have no idea why my last post was a copy of the previous one. Webmail choking
on a hairball.
It was supposed to say:
===
Oops, :name does break things, e.g.
if x :return
So, ::name or &name or |name or whatever.
I'm very amused by all the jokes about turning python into perl
At 01:51 PM 7/22/2010 +0100, Martin v. Löwis wrote:
At EuroPython, I sat down with Brett and we propose an approach
how namespace packages get along with import hooks. I reshuffled
the order in which things get done a little bit, and added a
section that elaborates on the hooks.
Basically, a fin
On 7/22/2010 5:45 AM, python-dev-requ...@python.org wrote:
Message: 10
Date: Thu, 22 Jul 2010 16:04:00 +0200
From: Bartosz Tarnowski
To:python-dev@python.org
Subject: [Python-Dev] Set the namespace free!
Message-ID:<4c484fd0.2080...@zlotniki.pl>
Content-Type: text/plain; charset=UTF-8; format=flo
Thanks for writing this, Tim.
On 7/21/10 11:11 AM, Tim Golden wrote:
The issue of a __format__ equivalent for bytes was also raised as was the
idea of object methods to render an object as string or bytes, which could
be used in the polymorphic functions above.
Does this mean bytes.__format__
On Wed, Jul 21, 2010 at 9:26 PM, Steve Holden wrote:
> On 7/21/2010 6:45 PM, Alexander Belopolsky wrote:
>> On Wed, Jul 21, 2010 at 1:42 PM, Benjamin Peterson
>> wrote:
>> ..
>>> True, but the tests in that file are (mostly?) all about line tracing.
>>>
>>
>> Hopefully this will change soon. :-)
oops, :name does break things, e.g
if x :return
So, it could be ::name or |name or &name or !name or whatever.
From: gregory.smi...@sympatico.ca
To: python-dev@python.org
Subject: RE: [Python-Dev] Set the namespace free!
Date: Thu, 22 Jul 2010 16:24:27 +
I agree with the ide
I agree with the idea, but a far less radical change is needed to get the
desired result.
The basic idea is this: it should be possible to use any name as an identifier
in the syntax, including names
like 'while' and 'import'. But there is no need to mess up the entire language
to allow this
(e
>
> !for boo in foo:
!if boo is !None:
!print(hoo)
!else:
!return !sorted(woo)
I feel most people could not bear such a difficult syntax. Why have I to
type so much '!'s ?
On Thu, Jul 22, 2010 at 10:04 PM, Bartosz Tarnowski <
bartosz-tarnow...@zlotniki.pl> wrote:
>
> Hel
At EuroPython, I sat down with Brett and we propose an approach
how namespace packages get along with import hooks. I reshuffled
the order in which things get done a little bit, and added a
section that elaborates on the hooks.
Basically, a finder will need to support a find_path method,
return a
On Thu, Jul 22, 2010 at 11:25 AM, Eli Bendersky wrote:
>>> .. shouldn't the recommended
>>> way to run a module as a script be python -m modname? As in
>>>
>>> $ python -m test.regrtest test_spam
..
> So, how can a decision be reached on this issue? I'd like to fix the
> relevant docs because cur
I believe that Pat Campbell is responsible for handling contributor
agreements. I'm trying to find out if we have one from Stuart Sheldon.
Could someone in the know please forward this to Pat, then we'll be
able to move these issues.
TIA.
Mark Lawrence.
On Thu, Jul 22, 2010 at 10:37 AM, Antoine Pitrou wrote:
> On Thu, 22 Jul 2010 16:54:58 +0100
> Georg Brandl wrote:
>>
>> That also has the advantage of introducing a measure of much needed
>> compatibility with industry-leading web programming languages.
>
> Also, Python would gain much needed fl
On Thu, 22 Jul 2010 16:54:58 +0100
Georg Brandl wrote:
>
> You raise a good point. However, I'd rather explicitly signify names instead
> of keywords:
>
> for $boo in $foo:
> if $boo is $None:
> print($hoo)
> else:
> return sorted($woo)
>
> That also has the advantage o
On Tue, Jul 20, 2010 at 20:34, Éric Araujo wrote:
>> Sorry to add the third way to the mix, but shouldn't the recommended
>> way to run a module as a script be python -m modname? As in
>>
>> $ python -m test.regrtest test_spam
>
> This is true but orthogonal to our problem, which is that
> :progr
On Thu, Jul 22, 2010 at 7:42 AM, Georg Brandl wrote:
> Am 22.07.2010 14:12, schrieb Nick Coghlan:
>> On Thu, Jul 22, 2010 at 9:34 PM, Georg Brandl wrote:
>>> So, I thought there wasn't a difference in performance for this use case
>>> (which is compiling a lot of regexes and matching most of them
On Thu, Jul 22, 2010 at 11:54 AM, Georg Brandl wrote:
..
> That also has the advantage of introducing a measure of much needed
> compatibility with industry-leading web programming languages.
Looks like our messages crossed in flight.
pathologically-eclecticly-yours
_
On Thu, Jul 22, 2010 at 10:08 PM, stefan brunthaler
wrote:
>> Is the source code under an open source non-copyleft license?
>>
> I am (unfortunately) not employed or funded by anybody, so I think
> that I can license/release the code as I see fit.
If you did this work under your PhD program, you
On Thu, Jul 22, 2010 at 10:41 AM, Jesse Noller wrote:
..
> I'm not a fan of this - I'd much prefer[1] that we use the exclamation
> point to determine scope:
>
> foobar - local
> !foobar - one up
> !!foobar - higher than the last one
> !!!foobar - even higher in scope
>
> We could do the inverse a
On Thu, Jul 22, 2010 at 10:04 AM, Bartosz Tarnowski <
bartosz-tarnow...@zlotniki.pl> wrote:
>
> Let all reserved words be preceded with some symbol, i.e. "!" (exclamation
> mark). This goes also for standard library global identifiers.
>
> !for boo in foo:
>!if boo is !None:
>!print(hoo
Am 22.07.2010 15:04, schrieb Bartosz Tarnowski:
>
> Hello, guys.
>
> Python has more and more reserved words over time. It becomes quite annoying,
> since you can not use variables and attributes of such names. Suppose I want
> to
> make an XML parser that reads a document and returns an objec
On Thu, Jul 22, 2010 at 10:04 AM, Bartosz Tarnowski
wrote:
>
> Hello, guys.
>
> Python has more and more reserved words over time. It becomes quite
> annoying, since you can not use variables and attributes of such names.
> Suppose I want to make an XML parser that reads a document and returns an
On Jul 16, 2010, at 12:40 PM, Matthias Klose wrote:
>I like the proposal, but IMO it is too unspecific about the abi tag.
>Assume that an extension is built with such a configured python and
>then tried to run with an abi compatible configured python, but with a
>slightly different version tag, th
Hello all,
PEP 360 - “Externally Maintained Packages” seems to have outdated
contents.
First of all, I don't think Optik and wsgiref are externally
maintained anymore (both seem unmaintained by their original authors).
Second, the version numbers mentioned there could be out of date too
(especial
Am 22.07.2010 14:12, schrieb Nick Coghlan:
> On Thu, Jul 22, 2010 at 9:34 PM, Georg Brandl wrote:
>> So, I thought there wasn't a difference in performance for this use case
>> (which is compiling a lot of regexes and matching most of them only a
>> few times in comparison). However, I found that
> The Springer link [1] at least shows the front page to give more of an
> idea as to what this is about.
>
Thanks, I forgot to mention the link.
> The idea does sound potentially interesting, although I'm not sure how
> applicable it will be with a full-blown LLVM-based JIT on the way for
> 3.3
On 10:33 am, solip...@pitrou.net wrote:
On Thu, 22 Jul 2010 17:50:00 +0900
"Stephen J. Turnbull" wrote:
I think that's Antoine's PEP 3151. Interestingly, he doesn't mention
EINVAL at all.
http://www.python.org/dev/peps/pep-3151/
That's right. It is based on a survey of existing exception-c
On Thu, Jul 22, 2010 at 9:22 PM, stefan brunthaler
wrote:
> I wonder whether you would be interested in integrating these
> optimizations with the Python 3 distribution, hence this mail. I could
> send copies of the papers, as well as provide my prototype source code
> to interested members of the
On 22 July 2010 14:14, Xavier Morel wrote:
> getattr(elem, 'param') I believe, rather than elem.getattr('param')
Doh! You're absolutely right, of course.
--
Cheers,
Simon B.
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mail
Am 22.07.2010 13:29, schrieb Antoine Pitrou:
> Le jeudi 22 juillet 2010 à 07:23 -0500, Benjamin Peterson a écrit :
>> 2010/7/22 Antoine Pitrou :
>> > On Thu, 22 Jul 2010 08:51:57 +0100
>> > Brett Cannon wrote:
>> >>
>> >> That's an option. I just remember Tim bringing up something about that
>> >>
On 2010-07-22, at 14:45 , Simon Brunning wrote:
> On 22 July 2010 15:04, Bartosz Tarnowski
> wrote:
>> What should I do then, when the attribute is a reserver word?
>
> You would use elem.getattr('param'). That's what it's for.
getattr(elem, 'param') I believe, rather than elem.getattr('param'
On Thu, Jul 22, 2010 at 9:34 PM, Georg Brandl wrote:
> So, I thought there wasn't a difference in performance for this use case
> (which is compiling a lot of regexes and matching most of them only a
> few times in comparison). However, I found that looking at the regex
> caching is very importan
> Is the source code under an open source non-copyleft license?
>
I am (unfortunately) not employed or funded by anybody, so I think
that I can license/release the code as I see fit.
> Have you checked that the whole regression test suite passes?
>
Currently, I am sure my prototype will not pass
2010/7/22 Antoine Pitrou :
> Le jeudi 22 juillet 2010 à 07:23 -0500, Benjamin Peterson a écrit :
>> 2010/7/22 Antoine Pitrou :
>> > On Thu, 22 Jul 2010 08:51:57 +0100
>> > Brett Cannon wrote:
>> >>
>> >> That's an option. I just remember Tim bringing up something about that
>> >> approach that did
Note that I'll revert Doc/distutils as well, but I need to check first
with Ronald a few Mac OS X points.
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/opt
Hello
As decided during the summit, I've reverted Distutils in the py3k
branch, to its release3.1-maint state. This was already done in 2.7.
I will only work on bugfixes for now on for distutils. Everything new
is done in distutils2. So if you have a feature request, use the
distutils2 component
On Thu, 22 Jul 2010, Bartosz Tarnowski wrote:
[]
My proposal: let's make a syntax change.
I'm pretty sure this belongs on python-ideas.
Let all reserved words be preceded with some symbol, i.e. "!" (exclamation
mark). This goes also for standard library global identifiers.
!for boo in
On 22 July 2010 15:04, Bartosz Tarnowski wrote:
> What should I do then, when the attribute is a reserver word?
You would use elem.getattr('param'). That's what it's for.
> Let all reserved words be preceded with some symbol, i.e. "!" (exclamation
> mark).
Oh, God, no.
This would be better off
On Thu, 22 Jul 2010 13:22:48 +0200
stefan brunthaler wrote:
>
> I wonder whether you would be interested in integrating these
> optimizations with the Python 3 distribution, hence this mail. I could
> send copies of the papers, as well as provide my prototype source code
> to interested members o
Hello, guys.
Python has more and more reserved words over time. It becomes quite annoying,
since you can not use variables and attributes of such names. Suppose I want to
make an XML parser that reads a document and returns an object with attributes
corresponding to XML element attributes:
Le jeudi 22 juillet 2010 à 07:23 -0500, Benjamin Peterson a écrit :
> 2010/7/22 Antoine Pitrou :
> > On Thu, 22 Jul 2010 08:51:57 +0100
> > Brett Cannon wrote:
> >>
> >> That's an option. I just remember Tim bringing up something about that
> >> approach that didn't quite work as a complete replac
2010/7/22 Antoine Pitrou :
> On Thu, 22 Jul 2010 08:51:57 +0100
> Brett Cannon wrote:
>>
>> That's an option. I just remember Tim bringing up something about that
>> approach that didn't quite work as a complete replacement for __del__.
>>
>> Basically the whole setting a module's globals to None
On Thu, 22 Jul 2010 07:02:33 pm Stephen J. Turnbull wrote:
> OTOH I think as quick as possible an answer is a good idea here. It
> saves the intended audience the thought about whether to reply or
> not, and an instant, constructive answer says that somebody cares.
+1
I think that waiting "a d
On Thu, 22 Jul 2010 08:51:57 +0100
Brett Cannon wrote:
>
> That's an option. I just remember Tim bringing up something about that
> approach that didn't quite work as a complete replacement for __del__.
>
> Basically the whole setting a module's globals to None was done before gc
> came into the
Hello,
during the last year, I have developed a couple of quickening-based
optimizations for the Python 3.1 interpreter. As part of my PhD
programme, I have published a first technique that combines quickening
with inline caching at this year's ECOOP, and subsequently extended
this technique to op
On Fri, Jul 16, 2010 at 6:08 PM, Georg Brandl wrote:
> Nevertheless, the authoritative reference for our regex engine is its
> docs, i.e. http://docs.python.org/library/re.html -- and that states
> clearly that inline flags apply to the whole regex.
>
>> I think with a new regex implementation, no
On Thu, Jul 22, 2010 at 06:02:33PM +0900, Stephen J. Turnbull wrote:
> Oleg Broytman writes:
> > On Wed, Jul 21, 2010 at 07:28:24PM -0600, average wrote:
> > > As to your question of how best to handle inquiries from the blue or
> > > "noisy questions", I personally prefer the following (only sl
Am 13.07.2010 15:35, schrieb Antoine Pitrou:
> On Tue, 13 Jul 2010 15:20:23 +0100
> Michael Foord wrote:
>> On 13/07/2010 15:17, Reid Kleckner wrote:
>> > On Mon, Jul 12, 2010 at 2:07 PM, Nick Coghlan wrote:
>> >
>> >> MRAB's module offers a superset of re's features rather than a subset
>> >
On Thu, 22 Jul 2010 17:50:00 +0900
"Stephen J. Turnbull" wrote:
> Greg Ewing writes:
> > Glyph Lefkowitz wrote:
> >
> > > The selection of RuntimeError in this particular case seems
> > > somewhat random and ad-hoc,
>
> Well, I guess we'd have to catch the person who wrote the code and
> ask
Oleg Broytman writes:
> On Wed, Jul 21, 2010 at 07:28:24PM -0600, average wrote:
> > As to your question of how best to handle inquiries from the blue or
> > "noisy questions", I personally prefer the following (only slightly
> > tongue-in-cheek):
> >
> > ...After a sufficient period of wait
On Jul 21, 2010, at 04:11 PM, Tim Golden wrote:
>The email module needs some work in Py3. David Murray has been given
>some money by the PSF but needs more from other sources to complete
>the work. This is hampered by the legalities around commercial
>organisations making donations to not-for-prof
Greg Ewing writes:
> Glyph Lefkowitz wrote:
>
> > The selection of RuntimeError in this particular case seems
> > somewhat random and ad-hoc,
Well, I guess we'd have to catch the person who wrote the code and
ask.
> Maybe this is something that could be considered in the
> exception hierar
On Thu, Jul 22, 2010 at 9:51 AM, Brett Cannon wrote:
>
>
> On Wed, Jul 21, 2010 at 16:58, Antoine Pitrou wrote:
>>
>> On Wed, 21 Jul 2010 11:42:00 -0400
>> Jesse Noller wrote:
>> > On Wed, Jul 21, 2010 at 11:11 AM, Tim Golden
>> > wrote:
>> > [...snip...]
>> > > A messy discussion turned on the
On Wed, Jul 21, 2010 at 16:58, Antoine Pitrou wrote:
> On Wed, 21 Jul 2010 11:42:00 -0400
> Jesse Noller wrote:
> > On Wed, Jul 21, 2010 at 11:11 AM, Tim Golden
> wrote:
> > [...snip...]
> > > A messy discussion turned on the question of garbage collection of
> module
> > > objects, and the ord
Glyph Lefkowitz wrote:
The selection of RuntimeError in this particular case seems somewhat random and
ad-hoc,
Indeed -- usually a RuntimeError indicates that something
concerning the internals of Python itself is screwed up,
e.g. attempting to execute invalid bytecode.
The fact that it turn
80 matches
Mail list logo
