On 21/08/2012 06:34, mar...@v.loewis.de wrote:
Zitat von "Juancarlo Añez (Apalala)" :
It seems that Jython is under the Python Foundation, but I can't find
a roadmap, a plan, or instructions about how to contribute to it
reaching 2.7 and 3.3.
Are there any pages that describe the process?
Zitat von Terry Reedy :
I was and am posting here in response to a certain French writer who
dislikes the fact that 3.3 unicode favors text written with the
first 256 code points, which do not include all the characters
needed for French, and do not include the euro symbol invented years
I was contemplating that option indeed. Sébastien Sablé seemed to
have the same aim. Would you know any other such efforts?
I believe Kristjan Jonsson has a port as well.
Regards,
Martin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail
On 8/21/2012 9:04 AM, Victor Stinner wrote:
2012/8/18 Terry Reedy :
The issue came up in python-list about string operations being slower in
3.3. (The categorical claim is false as some things are actually faster.)
Yes, some operations are slower, but others are faster :-)
Yes, that is what
On 19.08.12 00:17, Terry Reedy wrote:
This is one of the 3.3 improvements. But since the results are equal:
('a'*1000).encode() == ('a'*1000).encode(encoding='utf-8')
and 3.3 should know that for an all-ascii string, I do not see why
adding the parameter should double the the time. Another issue
Thanks for the quick response.
>> [...] A compiler upgrade is a feature, so the change to
>> VS2010 could only be applied to the version actively receiving new
>> features, which at the time was 3.3.
>
> But this does not prevent anyone from creating and maintaining such a
> patch, outside of the
On Wed, 22 Aug 2012 03:25:21 +1000
Steven D'Aprano wrote:
> On 21/08/12 23:04, Victor Stinner wrote:
>
> > I don't like the timeit module for micro benchmarks, it is really
> > unstable (default settings are not written for micro benchmarks).
> [...]
> > I wrote my own benchmark tool, based on ti
On Tue, Aug 21, 2012 at 1:56 PM, Xavier Morel wrote:
> As a side-note, every time I use timeit programmatically, it annoys me that
> this behavior is not available and has to be implemented manually.
You are not alone:
http://bugs.python.org/issue6422
___
Xavier Morel, 21.08.2012 19:56:
> On 21 août 2012, at 19:25, Steven D'Aprano wrote:
>> On 21/08/12 23:04, Victor Stinner wrote:
>>> I don't like the timeit module for micro benchmarks, it is really
>>> unstable (default settings are not written for micro benchmarks).
>> [...]
>>> I wrote my own be
On 21 août 2012, at 19:25, Steven D'Aprano wrote:
> On 21/08/12 23:04, Victor Stinner wrote:
>
>> I don't like the timeit module for micro benchmarks, it is really
>> unstable (default settings are not written for micro benchmarks).
> [...]
>> I wrote my own benchmark tool, based on timeit, to ha
On 21/08/12 23:04, Victor Stinner wrote:
I don't like the timeit module for micro benchmarks, it is really
unstable (default settings are not written for micro benchmarks).
[...]
I wrote my own benchmark tool, based on timeit, to have more stable
results on micro benchmarks:
https://bitbucket.
On Tue, 21 Aug 2012 17:20:14 +0200
Andrea Griffini wrote:
> > My benchmark.py script calibrates automatically the number of loops to
> > take at least 100 ms, and then repeat the test during at least 1.0
> > second.
> >
> > Using time instead of a fixed number of loops is more reliable because
> >
Am 21.08.2012 17:01, schrieb mar...@v.loewis.de:
> In the specific case, this isn't actually the limiting factor.
> Instead, it's binary compatibility: binaries compiled with VS 2010
> are incompatible (in some cases) with those compiled with VS 2008.
> So if the python.org binaries were released a
print(timeit("c in a", "c = '…'; a = 'a'*1000+c")) # ord(c) = 8230
I'm not sure that I read your benchmark correctly: you write c='...'
Apparenly you didn't - or your MUA was not able to display it
correctly. He didn't say
'...' # U+002E U+002E U+002E, 3x FULL STOP
but
'…' # U+2026, HORIZ
> My benchmark.py script calibrates automatically the number of loops to
> take at least 100 ms, and then repeat the test during at least 1.0
> second.
>
> Using time instead of a fixed number of loops is more reliable because
> the test is less dependent on the system activity.
I've also been bit
Zitat von Brian Curtin :
On Tue, Aug 21, 2012 at 5:24 AM, Luc Bourhis wrote:
Greetings,
it is my understanding that the patches floating around the net to
support Visual Studio 2010 to compile the Python core and for
distutils will never be accepted and therefore that the 2.7 line is
s
Zitat von Luc Bourhis :
it is my understanding that the patches floating around the net to
support Visual Studio 2010 to compile the Python core and for
distutils will never be accepted and therefore that the 2.7 line is
stuck to VS 2008 for the remaining of its life. Could you please
co
2012/8/21 Brian Curtin :
> On Tue, Aug 21, 2012 at 5:24 AM, Luc Bourhis wrote:
>> Greetings,
>>
>> it is my understanding that the patches floating around the net to support
>> Visual Studio 2010 to compile the Python core and for distutils will never
>> be accepted and therefore that the 2.7 li
On Tue, Aug 21, 2012 at 5:24 AM, Luc Bourhis wrote:
> Greetings,
>
> it is my understanding that the patches floating around the net to support
> Visual Studio 2010 to compile the Python core and for distutils will never be
> accepted and therefore that the 2.7 line is stuck to VS 2008 for the
2012/8/18 Terry Reedy :
> The issue came up in python-list about string operations being slower in
> 3.3. (The categorical claim is false as some things are actually faster.)
Yes, some operations are slower, but others are faster :-) There was
an important effort to limit the overhead of the PEP 3
On Tue, Aug 21, 2012 at 10:01 PM, R. David Murray wrote:
> I think it is an important and subtle point that this happens at "compile
> time" rather than "run time". Subtle in that it is not at all obvious
> (as this question demonstrates), and important in that it does have
> performance implicat
On Tue, 21 Aug 2012 17:47:28 +1000, Nick Coghlan wrote:
> On Tue, Aug 21, 2012 at 11:55 AM, Ezio Melotti wrote:
> >> +String literals that are part of a single expression and have only
> >> whitespace
> >> +between them will be implicitly converted to a single string literal.
> >> +
> >
> >
> > I
Greetings,
it is my understanding that the patches floating around the net to support
Visual Studio 2010 to compile the Python core and for distutils will never be
accepted and therefore that the 2.7 line is stuck to VS 2008 for the remaining
of its life. Could you please confirm that?
Best wi
On Tue, Aug 21, 2012 at 11:55 AM, Ezio Melotti wrote:
>> +Sequence Types --- :class:`list`, :class:`tuple`, :class:`range`
>> +
>> +
>
>
> These 3 links in the section title redirect to the functions.html page. I
> think it would be
24 matches
Mail list logo
