ieve it's accidental that match-case sequence patterns won't
match str, bytes or bytearrray objects - regexen are the tool already
optimised for that purpose, so it's quite impressive that you are
managing to approach the same level of performance!
Kind regards,
Steve
On Wed,
funnily - slower! Using the clumsy if-guards felt slow but isn't.
Then I generated functions even, with everything as constants,
and now the SPM version in fact out-performs the regex slightly!
But at last, I found an even faster and correct algorithm
by a different approach, which ends now
On 02.08.23 13:23, Barry wrote:
On 2 Aug 2023, at 12:03, Christian Tismer-Sperling
wrote:
Hi folks,
I just used Structural Pattern Matching quite intensively and I'm
pretty amazed of the new possibilities.
But see this code, trying to implement Mark Pilgrim's regex
algorithm
return 4 * 1000, r
So what is missing seems to be a notion of const-ness, which
could be dynamically deduced. Am I missing something?
--
Christian Tismer-Sperling:^) tis...@stackless.com
Software Consulting : http://www.stackless.com/
Strandstraße 37
PyPy
might create much interest for both projects.
Cheers - Chris
--
Christian Tismer-Sperling:^) tis...@stackless.com
Software Consulting : http://www.stackless.com/
Strandstraße 37 : https://github.com/PySide
24217 Schönberg : GPG key -> 0xF
think to send an official announce when this is available on pip.
This effort marks the completion of my PyPy support, which began
in 2003 and ended involuntarily in 2006 due to a stroke.
All the best -- Chris
--
Christian Tismer-Sperling:^) tis...@stackless.com
Software Consulting
),
can't we think of replacing it somehow by functions in the case
of the Limited API? The API is so often used that it would make sense
to _always_ don't crash deeply nested structures.
Or do you think it makes no sense at all? Then let's turn it
into a no-op. But the current mixed
Pardon, I meant "there is no Python 3.8 version, yet".
And this is wrong, the MacOS pip install shows
PyQt5-5.13.2-5.13.2-cp35.cp36.cp37.cp38-abi3-macosx_10_6_intel.whl
So probably we have some bad oversight, somewhere.
Cheers -- Chris
On 12.12.19 13:48, Christian Tismer w
ited API a bit, because we have to dynamically
figure that out in order to be version-independent.
I am not so sure if that whole change was worth to break it?
Cheers -- Chris
--
Christian Tismer-Sperling:^) tis...@stackless.com
Software Consulting : http://www.stackless.com/
S
e same problem, since there is no 5.14 version yet ;-)
> On 2019-12-11 23:48, Christian Tismer wrote:
>> Hi all,
>>
>> Sorry for the noise, I was wrong, and I retract.
>> I was somehow mislead and hunted a phantom.
>
> Does that mean that there was never a problem?
&
Hi all,
Sorry for the noise, I was wrong, and I retract.
I was somehow mislead and hunted a phantom.
Best - Chris
On 10.12.19 00:29, Christian Tismer wrote:
> On 09.12.19 23:26, Nick Coghlan wrote:
>>
>>
>> On Tue., 10 Dec. 2019, 5:17 am MRAB, > <mailto:pyt...@
Thanks in advance,
> Victor
>
> Le mar. 10 déc. 2019 à 14:18, Christian Tismer a écrit
> :
>>
>> Hi Łukasz,
>>
>> tonite I found a critical bug that affects all heaptype extension
>> classes with a custom (not PyType_Type) type.
>>
>> the b
On 10.12.19 14:28, Łukasz Langa wrote:
>
>> On 10 Dec 2019, at 14:16, Christian Tismer > <mailto:tis...@stackless.com>> wrote:
>>
>> Please let me know how you want to proceed.
>> This is a critical error, producing negative refcounts.
>
> Is there
Sorry, I sent the fixed version.
These two incref's are missing!
On 10.12.19 14:16, Christian Tismer wrote:
> Hi Łukasz,
>
> tonite I found a critical bug that affects all heaptype extension
> classes with a custom (not PyType_Type) type.
>
> the bug is i
t; To unsubscribe send an email to python-dev-le...@python.org
> https://mail.python.org/mailman3/lists/python-dev.python.org/
> Message archived at
> https://mail.python.org/archives/list/python-dev@python.org/message/IGJ6ZOAOT2WFY5ZIPRQNTHOSUMPUAO2H/
> Code of Conduct: http://
On 09.12.19 23:26, Nick Coghlan wrote:
>
>
> On Tue., 10 Dec. 2019, 5:17 am MRAB, <mailto:pyt...@mrabarnett.plus.com>> wrote:
>
> On 2019-12-09 18:22, Christian Tismer wrote:
> >
> >
> > Hi Nick,
> >
> > afte
On 08.12.19 09:49, Nick Coghlan wrote:
> On Fri., 6 Dec. 2019, 3:31 am Christian Tismer, <mailto:tis...@stackless.com>> wrote:
>
> Hi guys,
>
> during the last few weeks I have been struggling quite much
> in order to make PySide run with Python 3.8 at
On 08.12.19 09:49, Nick Coghlan wrote:
> On Fri., 6 Dec. 2019, 3:31 am Christian Tismer, <mailto:tis...@stackless.com>> wrote:
>
> Hi guys,
>
> during the last few weeks I have been struggling quite much
> in order to make PySide run with Python 3.8 at
I would really like to understand the reason for this unexpected effect.
Does this ring a bell? I have no clue what is wrong with PySide, if it
is wrong at all.
Thanks -- Chris
--
Christian Tismer :^) tis...@stackless.com
Software Consulting : http://www.stackless.com/
Ka
On 12.08.19 10:52, Ivan Levkivskyi wrote:
> On Thu, 8 Aug 2019 at 17:17, Christian Tismer <mailto:tis...@stackless.com>> wrote:
>
> Yes, that's what I mean.
> Probably retval or whatever people prefer would be adequate,
> with a special rule if that na
ot! Especially the builtins idea
is really great :-P
Cheers - Chris
p.s.: How about adding @private as well?
There are cases where I would like to do the opposite:
__all__ = dir()
@private
_some_private_func_1(...): ...
...
@private
_some_private_func_n(...): ...
not-too-serio
approach is to go with the
> generic SyntaxError as Barry suggests. I'll update my PRs accordingly.
Totally agree. It is fine to have SyntaxError now and go for
one or more new subclasses for a whole bunch of errors at
a later time, fixing more things in a more consistent way
xError after the parser is finished, in a
> subsequent pass. Is it really a syntax error if pgen doesn't object to
> it? In current CPython, the answer is yes.
...
OT: Thanks for the interesting read!
I am excited which way it will continue.
--
Christian Tismer :^)
hy not name it 'return_value' or 'result' or
> 'retval' or something like that?
>
> On Thu, Aug 8, 2019 at 1:43 AM Christian Tismer <mailto:tis...@stackless.com>> wrote:
>
> Hi Guido,
>
> If a C++ function already has a return value,
On 08.08.19 17:20, Ronald Oussoren via Python-Dev wrote:
>
>
>> On 8 Aug 2019, at 17:12, Christian Tismer > <mailto:tis...@stackless.com>> wrote:
>>
>> Hi Ronald,
>>
>> sure, the tuple is usually not very interesting; people look it up
>>
t; someclass) -> (bool, int)
>
> I rarely, if ever, see code that actually stores the return tuple as-is.
> The return tuple is just deconstructed immediately, like “x, y =
> getpoint(mypoint)”.
>
> Ronald
> —
>
> Twitter: @ronaldoussoren
> Blog: https://blog.ronaldou
gt; https://mail.python.org/mailman3/lists/python-dev.python.org/
> Message archived at
> https://mail.python.org/archives/list/python-dev@python.org/message/V2EDFDJGXRIDMKJU3FKIWC2NDLMUZA2Y/
>
--
Christian Tismer :^) tis...@stackless.com
Software Consulting :
e
> checker about the number of anonymous fields.
>
> --Guido
>
> On Wed, Aug 7, 2019 at 1:51 AM Christian Tismer <mailto:tis...@stackless.com>> wrote:
>
> Hi all,
>
> Ok, I am about to implement generation of such structures
> automatically usi
(yet :-)
cheers -- Chris
On 30.07.19 17:10, Guido van Rossum wrote:
> I think I have to agree with Petr. Define explicit type names.
>
> On Tue, Jul 30, 2019 at 2:45 AM Paul Moore <mailto:p.f.mo...@gmail.com>> wrote:
>
> On Tue, 30 Jul 2019 at 09:33, Christian
de, I assume you're using the C-API. If that's the
> case, check out Struct Sequences, the "C equivalent of named tuples".
> For example, the result of "os.stat()" is a struct sequence.
>
> https://docs.python.org/3/c-api/tuple.html#struct-sequence-objects
>
le([("x", int), ("y", int)]): ...
cheers -- Chris
On 29.07.19 18:00, Guido van Rossum wrote:
> Can't you use the proper inline form of NamedTuple?
>
> def f() -> typing.NamedTuple("__f", [("x", int), ("y", int)]):
> ...
>
Cheers -- Chris
--
Christian Tismer :^) tis...@stackless.com
Software Consulting : http://www.stackless.com/
Karl-Liebknecht-Str. 121 : https://github.com/PySide
14482 Potsdam: GPG key -> 0xFB7BEE0E
phone +49 173 24 18 776 fax +
On 06.06.19 21:27, Brett Cannon wrote:
>
>
> On Thu, Jun 6, 2019 at 12:25 AM Christian Tismer <mailto:tis...@stackless.com>> wrote:
>
> On 05.06.19 02:21, Victor Stinner wrote:
> > So what is happening for this PEP since Python 3.8 beta1 has been
>
eature:
The set of modules in the stdlib has exactly that being in the
stdlib as a quality indicator.
I need now a structure that replaces that quality,
like
"This one is eligible to go into stdlib"
Do we have such a replacement implemented, already?
--
Christian Tismer
gt; Python-Dev@python.org <mailto:Python-Dev@python.org>
> https://mail.python.org/mailman/listinfo/python-dev
> <https://mail.python.org/mailman/listinfo/python-dev>
> Unsubscribe:
> https://mail.python.org/mailman/options/python-dev/steve%40holdenweb.com
So sorry that I was way too deep in development in spring
and did not read earlier about that PEP.
I was actually a bit reluctant about "yet another way to prove
Python no longer simple" and now even that Pascal-ish look! :-)
But this argument has completely sold me. Marvellous!
--
Answering myself:
PySequence_Check determines a sequence. See the docs.
len() can but does not have to exist.
The size is always limited.
After evicting my initial fault, this is now obvious.
Sorry about the noise.
On 22.06.18 13:17, Christian Tismer wrote:
> Hi Brett,
>
> becaus
out an exact definition what makes up a sequence?
Sorry if I'm again the only one who misunderstands the obvious :)
Best -- Chris
On 21.06.18 18:29, Brett Cannon wrote:
> Sorry, I don't quite follow.
>
> On Thu, 21 Jun 2018 at 08:50 Christian Tismer <mailto:tis...
the unlimited case, but
it seems still to be true that sequences are always finite.
Can someone please enlighten me?
--
Christian Tismer-Sperling:^) tis...@stackless.com
Software Consulting : http://www.stackless.com/
Karl-Liebknecht-Str. 121 : http://pyside.org
14482
On 03.06.18 13:18, Ronald Oussoren wrote:
>
>
>> On 3 Jun 2018, at 12:03, Christian Tismer wrote:
...
>>
>> I have written a script that scans all relevant header files
>> and analyses all sections which are reachable in the limited API
>> context.
&g
break.
I found exactly 7 locations where this is the case.
My PR will contain the 7 fixes plus the analysis script
to go into tools. Preparind that in the evening.
cheers -- Chris
--
Christian Tismer-Sperling:^) tis...@stackless.com
Software Consulting : http://www.
y it Qt starts using it
> then that will help us shake these things out... But it also means we
> need your help to catch these kinds of issues :-). Thanks!
>
> On Fri, Jun 1, 2018, 06:51 Christian Tismer <mailto:tis...@stackless.com>> wrote:
>
> Hi friends,
>
umber->nb_index != NULL)
This contradicts PEP 384, because there is no way for non-heaptype
types to access the nb_index field.
If nobody objects, I would like to submit a patch that adds the
function back when the limited API is active.
I think to fix that before Python 3.7 is out.
Ciao
stay compatible, and where
do you plan to deviate?
The reason that I'm asking is that by compatible I mean the
compatibility of PyPy. If you can reach that, and be it just
by a subset, then it makes sense to speak of Python.
Cheers - Chris
--
Christian Tismer-Sperling:^) tis...@stackless.co
igned for the purpose of allowing rapid
> experimentation with the language, is on topic for this list.
>
>
Well spoken!
--
Christian Tismer-Sperling:^) tis...@stackless.com
Software Consulting : http://www.stackless.com/
Karl-Liebknecht-Str. 121 : https://github.c
7;s totally messed up! But the fix should really be to
> fix this, not inventing a new feature.
>
> --
> --Guido van Rossum (python.org/~guido <http://python.org/~guido>)
>
>
> ___
> Python-Dev mailing list
> Python-Dev@python.org
> https://mai
Ok, I thought only about Windows where people often use shell=True.
I did not see that as a Linux problem, too.
Not meant as a proposal, just loud thinking... :-)
But as said, the incomplete escaping is a complete mess.
Ciao -- Chris
On 07.01.18 19:54, Christian Tismer wrote:
> By "nor
correct. And that is not
trivial, either.
On 07.01.18 18:22, Guido van Rossum wrote:
> On Sun, Jan 7, 2018 at 8:17 AM, Christian Tismer <mailto:tis...@stackless.com>> wrote:
>
> As a side note: In most cases where shell=True is found, people
> seem to need evalua
follow that code completely, but I see that it escapes double
> quotes. Why is there a need to escape other characters? Is there a
> definitive list of special characters somewhere?
>
> On Sun, Jan 7, 2018 at 8:17 AM, Christian Tismer <mailto:tis...@stackless.com>> wrote:
>
hon by some shell=True replacement (emulate_shell=True?)
to match the normal user expectations without using the shell?
Cheers - Chris
--
Christian Tismer-Sperling:^) tis...@stackless.com
Software Consulting : http://www.stackless.com/
Karl-Liebknecht-Str. 121 : https:/
test for
> the exception (I'm at the airport, hence why I don't know the name of
> the context manager; the warnings module docs actually have a sample on
> how best to write tests the involve warnings).
>
>
> On Fri, Nov 17, 2017, 01:34 Christian Tismer, <mailto:t
er.
My question:
Is that known, and is that intended?
To what extent are the test cases isolated from each other?
I do admit that my usage of warnings is somewhat special.
But it is very convenient to report many errors on remote servers.
Cheers -- Chris
--
Christian Tismer :^)
inherently hides any struct layout
> details behind PyObject*.
Thank you very much for the clarification.
I think we can live with the Python interface for now.
Now I'm sure that I'm going the way to go.
Cheers -- Chris
--
Christian Tismer :^) tis...@stackless.com
Softw
Hi Brett,
On 18.08.17 18:31, Brett Cannon wrote:
>
>
> On Fri, 18 Aug 2017 at 02:05 Christian Tismer <mailto:tis...@stackless.com>> wrote:
>
...
> Is it a bad idea to support signatures in Python 2 as well?
> Do I introduce a feature that should not exist
d much more internal knowledge as intended...
Well, I thought the existence of __signature__ might be a good reason
to switch to Python 3, but if I support Python 2, the advantage
is gone. But if it's ok with you, then I'll publish both versions.
Thanks a lot for the feedb
Cheers -- Chris
--
Christian Tismer :^) tis...@stackless.com
Software Consulting : http://www.stackless.com/
Karl-Liebknecht-Str. 121 : https://github.com/PySide
14482 Potsdam: GPG key -> 0xFB7BEE0E
phone +49 173 24 18 776 fax +49 (30) 700143-002
On 25.06.17 14:41, Serhiy Storchaka wrote:
> 25.06.17 15:06, Christian Tismer пише:
>> by chance, I stumbled over
>>
>> meth_get__qualname__
>>
>> in methodobject.c and
>>
>> calculate_qualname
>>
>> in descrobject.c .
>>
romFormat("%S.%S", type_qualname, descr->d_name);
To my knowledge, the "%S" character is undefined in C99 and C11.
Q: Why this character, and why this difference?
cheers - Chris
--
Christian Tismer :^) tis...@stackless.com
Software Consulting : http://www.
functions, and which parts of
> python call c++ functions. You can't do that with pdb.
>
>
>> On 13 Oct 2016, at 19:12, Christian Tismer > <mailto:tis...@stackless.com>> wrote:
>>
>> Hi Alexandru,
>>
>> I stumbled over this question a little
Hi Alexandru,
I stumbled over this question a little late by chance.
There is the possibility to use GDB, but it is most likely that you want to use
python's pdb module, instead.
Only in rare cases, when debugging the interpreter itself, you use gdb. For
debugging Python code, use pdb or som
parameter.
>
> Would that clarify?
Yes please, that would be a good place to document it. For some reason
I did not look up __future__.
Thanks -- Chris
On 01/10/16 14:17, Chris Angelico wrote:
On Sat, Oct 1, 2016 at 9:39 PM, Christian Tismer wrote:
The exec() script inherited the __futu
the future statement were implicitly there.
Is that a bug or a feature?
You can try the effect by "pip install dedent" and adding
the future statement there.
I'd like to know if this is a bug (and I think so)
--
Christian Tismer :^) tis...@stackless.com
Soft
.org/mailman/options/python-dev/brett%40python.org
>>
>>
>> ___
>> Python-Dev mailing list
>> Python-Dev@python.org
>> https://mail.python.org/mailman/listinfo/python-dev
>> Unsubscribe:
>> https://mail.python.org
ion end of 2013
with support for newer compilers, to begin with. After a while,
we stopped this, and I left the branch in a private, unmaintained
repository.
https://bitbucket.org/stackless-dev/stackless-private/branch/2.8-slp
Maybe you can make use of this, use it as you like it. You will
get an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 08.10.14 14:20, Donald Stufft wrote:
>
>> On Oct 8, 2014, at 6:16 AM, Christian Tismer
wrote:
>>
>>
>> ...
>>
>> So is there anything officially preferred, and should that go into pep 8?
>
> Some ed
n__ file.
I guess this is wrong and should be in the executable file,
which is __main__ .
cheers - Chris
- --
Christian Tismer :^) tis...@stackless.com
Software Consulting : http://www.stackless.com/
Karl-Liebknecht-Str. 121 : http://www.py
V with an extent over more
than 10 years.
I believe, such a thing does not exist for the Python 3.X series
at all. My impression is that no 3.X user ever would want to stick
with any older version.
Is that true, or am I totally wrong?
cheers -- Chris
- --
Christian Tismer
buffer protocol"""?
cheers - Chris
--
Christian Tismer :^) tis...@stackless.com
Software Consulting : http://www.stackless.com/
Karl-Liebknecht-Str. 121 : http://www.pydica.net/
14482 Potsdam: GPG key -> 0xFB7B
10%), but my
> management at least is very supportive of my participation and keen to
> keep Python running well.
>
Very nice, great to read this.
Welcome from me as well!
cheers - Chris
--
Christian Tismer :^) tis...@stackless.com
Software Consulting : http://www.st
On 16/04/14 16:35, Antoine Pitrou wrote:
> On Wed, 16 Apr 2014 09:39:34 +0200
> Christian Tismer wrote:
>>
>> I think in cases like hg command line scripts there is no need
>> to import site just for hg scripts.
>
> If you don't import site you won't be
van Rossum (python.org/~guido <http://python.org/%7Eguido>)
>
>
> _______
> Python-Dev mailing list
> Python-Dev@python.org
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe:
> https://mail.python.org/mailman/opt
On 12.04.14 01:55, Ethan Furman wrote:
> On 04/11/2014 02:01 PM, Christian Tismer wrote:
>>
>> I have these style problems with several modules that I am reluctant to
>> use, therefore. I know that I'm pretty alone with that.
>
> You are not alone in that.
Funny n
Hi Chris,
On 11/04/14 21:50, Chris Barker wrote:
> On Thu, Apr 10, 2014 at 7:12 PM, Christian Tismer wrote:
>
>> Then I rather often see things like this:
>>
>> class someclass(object):
>> # note that there is no comment about argument destruction...
>>
Thank you too, Tres.
Somehow I had a brain shortcut and forgot that
the dict is locally generated, *because* of the stars.
Good to become adjusted and restarted, sorry about the noise.
ciao - Chris
On 11/04/14 05:48, Tres Seaver wrote:
> On 04/10/2014 10:12 PM, Christian Tismer wrote:
>
r, and the whole reasoning chain
was pointless, therefore.
Thanks and cheers - Chris
> On Thu, Apr 10, 2014 at 10:12 PM, Christian Tismer
> wrote:
>
>> Hi guys,
>>
>> I tried to find advice for hours, but failed so fer, so here is my
>> question:
>>
>&g
ot;arguments may be
destroyed by default".
What do you think? Is this bad style and should be noticed somewhere,
or is the caller supposed to protect the arguments, or are my worries
useless?
Thanks & cheers -- Chris
--
Christian Tismer :^) <mailto:tis...@stackless.c
ething different
when going out to the mailing list? Or maybe there is a filter in the
brains?
If one removes the word "Stackless" everywhere, the above text reads
still almost syntactic correctly, but changes it's meaning a lot.
--
Christian Tismer :^) <mailto:tis.
ss's) users. And based on the discussions here,
there are plenty of good alternatives.
+1 from me :-)
Thank you for that input! It was important and urgent, as I saw myself
jumping
into the wrong wagon, again.
--
Christian Tismer :^) <mailto:tis...@stackless.com>
Softwa
On 21/11/13 22:13, Glenn Linderman wrote:
On 11/21/2013 12:23 PM, Christian Tismer wrote:
Maybe I would generate a cpython and spython exe and support them
both in the same distribution?
That sounds cool, if possible.
Hooka Hooka!
Let's see if the nightmares agree :-)
--
Christian T
now for just that.
What I want is a workable CPython path for some customer (!=CCP) to use
for the next (maybe 5) years, and I want to build that now, for good.
I think you have helped me incredibly much, and we need to talk in private.
Cheers -- Chris
--
Christian Tismer :^) <mailt
On 21/11/13 19:59, Ethan Furman wrote:
On 11/21/2013 10:53 AM, Christian Tismer wrote:
So even if VS2010 exists only in the stackless branch, it is very likely
to get used as CPython VS 2010, and I again have the naming problem ...
What's wrong with calling it CPython VS 2010? And Stac
back-door,
and we cannot shut our eyes and pretend "hey it is Stackless",
because that is admittedly close to a fraud.
So even if VS2010 exists only in the stackless branch, it is very likely
to get used as CPython VS 2010, and I again have the naming problem ...
Yes Paul,
On 20.11.13 23:15, Paul Moore wrote:
On 20 November 2013 22:04, Christian Tismer wrote:
My question is not answered at all, sorry Joao!
I did not ask a teacher for his opinion on Stackless, but the community
about the
validity of pep 404.
I don't want a python 2.7 that doe
Hey Barry,
On 20.11.13 23:30, Barry Warsaw wrote:
On Nov 20, 2013, at 09:52 PM, Christian Tismer wrote:
Many customers are forced to stick with Python 2.X because of other products,
but they require a Python 2.X version which can be compiled using Visual
Studio 2010 or better. This is
nloadable and installable Python 2.8 that would
be incompatible with extensions compiled in Pypi would be tough. and I
doubt it could even be done without making your project look bad on
the process.
Can't you just mark it as "visual studio 2010" version instead?
js
-><-
the "Python 2.8" namespace never will clash
with CPython?
And if not, what do you suggest then?
It will be submitted by end of November, thanks for your quick responses!
all the best -- Chris
--
Christian Tismer :^) <mailto:tis...@stackless.com>
Software Consulting
python'
would make sense. And I'm asking the people with better knowledge of
these matters
than I have. (and not asking those who don't... ;-) )
cheers -- Chris
--
Christian Tismer :^) <mailto:tis...@stackless.com>
Software Consulting : Have a brea
completely to
provide a better solution.
I appreciate very much that Victor tried his best to fill that old gap.
And after
that breakage happened again, I think it is urgent to have an in-depth
discussion how that
situation should be treated in the future.
--
Christian Tismer
On 15.05.13 14:01, Stefan Drees wrote:
Hi Chris,
On 15.05.13 13:32 Christian Tismer wrote:
Hi Raymond,
On 08.01.13 15:49, Maciej Fijalkowski wrote:
On Mon, Dec 10, 2012 at 3:44 AM, Raymond Hettinger
wrote:
The current memory layout for dictionaries is
unnecessarily inefficient. It has a
n ratios stay true provided you don't overallocate entry
list. If you do overallocate you don't really gain that much (it all
depends vastly on details), or even loose in some cases. What do you
think should the strategy be?
What is the current status of this discussion?
I'd like t
don't think the given example is very helpful,
but adds confusion.
Where would I add such a complaint, usually?
Or should I simply fix it?
cheers - chris
--
Christian Tismer :^) <mailto:tis...@stackless.com>
Software Consulting : Have a break! Take a ride on Py
your projects, the movement becomes a reality. Just say that we all
need to
move on and cannot care about companies that ignore this necessity.
I agree it is hard to push things forward, when certain tools are just
supporting
2.x. My way to get over this is ranting, and porting some things, and
ming that loudly
enough, it will
eventually happen!
cheers - chris
--
Christian Tismer :^) <mailto:tis...@stackless.com>
Software Consulting : Have a break! Take a ride on Python's
Karl-Liebknecht-Str. 121 :*Starship* http://starship.python.net/
14482
will pique the
interest of commercial entities out there that have problems perfectly
suited to where this pattern excels (shared-nothing, highly concurrent),
much like the relationship that developed between Stackless and Eve
Online.
What do you think: does it make sense to think of
7;m shutting up, intentionally.)
--
Christian Tismer :^) <mailto:tis...@stackless.com>
Software Consulting : Have a break! Take a ride on Python's
Karl-Liebknecht-Str. 121 :*Starship* http://starship.python.net/
14482 Potsdam: PGP key -> http
Hi Lennart,
Sent from my Ei4Steve
On Feb 13, 2013, at 8:42, Lennart Regebro wrote:
>> Something is needed - a patch for PyPy or for the documentation I guess.
>
> Not arguing that it wouldn't be good, but I disagree that it is needed.
>
> This is only an issue when you, as in your proof, have
reader not to use in-place
add when it is not optimized.
If += is anyway a bit slower than other ways, forget it.
I would then maybe add a commend somewhere that says
"avoiding '+=' because it is not reliable" or something.
cheers - chris
--
Christian Tismer :^) &l
Hey Nick,
On 13.02.13 15:44, Nick Coghlan wrote:
On Wed, Feb 13, 2013 at 10:06 PM, Christian Tismer wrote:
To avoid such hidden traps in larger code bases, documentation is
needed that clearly gives a warning saying "don't do that", like CS
students learn for most other langu
es, it's jitted.
How about the .format() style: Is that jitted as well?
In order to get people to prefer .format over __mod__,
it would be nice if PyPy made this actually _faster_ :-)
--
Christian Tismer :^) <mailto:tis...@stackless.com>
Software Consulting :
is
more than 3 and some of them are literal strings.
Fixed: x = ('%s' * len(abcd)) % abcd
Which becomes in the new formatting style
x = ('{}' * len(abcd)).format(*abcd)
hmm, hmm, not soo nice
--
Christian Tismer :^) <mailto:tis...@stackless.
1 - 100 of 155 matches
Mail list logo
