in 681910 20120927 131113 Devin Jeanpierre jeanpierr...@gmail.com wrote:
On Thu, Sep 27, 2012 at 2:13 AM, Steven D'Aprano
steve+comp.lang.pyt...@pearwood.info wrote:
On Tue, 25 Sep 2012 09:15:00 +0100, Mark Lawrence wrote:
And a response:
http://data.geek.nz/python-is-doing-just-fine
Summary
Summary of that article:
Sure, you have all these legitimate concerns, but look, cake!
Quote : This piece argues that Python is an easy-to-learn
language that where you can be almost immediately productive in.
It is, but so is every other language. hello world is the
standard... follow the
On 27/09/2012 20:08, Terry Reedy wrote:
On 9/27/2012 5:33 AM, Steven D'Aprano wrote:
Nevertheless, I think there is something here. The consequences are
nowhere
near as dramatic as jmf claims, but it does seem that replace() has
taken a
serious performance hit. Perhaps it is unavoidable, but
On Sep 27, 5:11 pm, Devin Jeanpierre jeanpierr...@gmail.com wrote:
On Thu, Sep 27, 2012 at 2:13 AM, Steven D'Aprano
steve+comp.lang.pyt...@pearwood.info wrote:
On Tue, 25 Sep 2012 09:15:00 +0100, Mark Lawrence wrote:
And a response:
http://data.geek.nz/python-is-doing-just-fine
Summary
On Fri, 28 Sep 2012 05:08:24 -0700, rusi wrote:
On Sep 27, 5:11 pm, Devin Jeanpierre jeanpierr...@gmail.com wrote:
On Thu, Sep 27, 2012 at 2:13 AM, Steven D'Aprano
steve+comp.lang.pyt...@pearwood.info wrote:
On Tue, 25 Sep 2012 09:15:00 +0100, Mark Lawrence wrote: And a
response:
On Sep 28, 5:54 pm, Steven D'Aprano steve
+comp.lang.pyt...@pearwood.info wrote:
On Fri, 28 Sep 2012 05:08:24 -0700, rusi wrote:
On Sep 27, 5:11 pm, Devin Jeanpierre jeanpierr...@gmail.com wrote:
On Thu, Sep 27, 2012 at 2:13 AM, Steven D'Aprano
steve+comp.lang.pyt...@pearwood.info wrote:
On Sat, Sep 29, 2012 at 12:31 AM, Dennis Lee Bieber
wlfr...@ix.netcom.com wrote:
On Fri, 28 Sep 2012 14:37:21 +1000, Chris Angelico ros...@gmail.com
declaimed the following in gmane.comp.python.general:
For further details, poke around on the web; I'm sure you'll find
plenty of good blog
On Fri, Sep 28, 2012 at 8:58 AM, Chris Angelico ros...@gmail.com wrote:
Yes, MySQL has definitely improved. There was a time when its
unreliability applied to all your data too, but now you can just click
in InnoDB and have mostly-real transaction support etc. But there's
still a lot of work
On Sat, Sep 29, 2012 at 1:14 AM, Ian Kelly ian.g.ke...@gmail.com wrote:
On Fri, Sep 28, 2012 at 8:58 AM, Chris Angelico ros...@gmail.com wrote:
Yes, MySQL has definitely improved. There was a time when its
unreliability applied to all your data too, but now you can just click
in InnoDB and
On 09/27/2012 10:37 PM, Chris Angelico wrote:[...]
* MySQL is designed for dynamic web sites, with lots of reading and
not too much writing. Its row and table locking system is pretty
rudimentary, and it's quite easy for performance to suffer really
badly if you don't think about it. But if
On Thu, Sep 27, 2012 at 8:59 PM, alex23 wuwe...@gmail.com wrote:
On Sep 28, 2:17 am, Devin Jeanpierre jeanpierr...@gmail.com wrote:
Uncharitably, it's just a way of hiding one's head in the sand,
ignoring any problems Python has by focusing on what problems it
doesn't have.
But isn't that
On Fri, 28 Sep 2012 14:50:14 -0400, Devin Jeanpierre wrote:
I'm pretty sure nobody thinks Python is on a death march.
Don't be so sure. There's always *someone* complaining about something,
and they're usually convinced that (Language X) is on it's last legs
because (feature Y) is missing or
On Thu, 27 Sep 2012 15:37:35 +1000, Chris Angelico wrote:
On Thu, Sep 27, 2012 at 10:44 AM, Steven D'Aprano
steve+comp.lang.pyt...@pearwood.info wrote:
While PyPy is still a work in progress, and is not anywhere near as
mature as (say) gcc or clang, it should be considered production-ready.
On Thu, Sep 27, 2012 at 4:01 PM, Steven D'Aprano
steve+comp.lang.pyt...@pearwood.info wrote:
On Thu, 27 Sep 2012 15:37:35 +1000, Chris Angelico wrote:
Assuming it manages to catch up with Py3, which a decade makes entirely
possible, this I can well believe. And while we're sounding all hopeful,
On Tue, 25 Sep 2012 09:15:00 +0100, Mark Lawrence wrote:
Hi all,
I though this might be of interest.
http://www.ironfroggy.com/software/i-am-worried-about-the-future-of-
python
And a response:
http://data.geek.nz/python-is-doing-just-fine
--
Steven
--
On 27.09.12 09:08, Chris Angelico wrote:
LAMP usually means PHP these days. There's a lot of that around.
And Cyrillic Р means Ruby. :-P
--
http://mail.python.org/mailman/listinfo/python-list
On Wed, 26 Sep 2012 08:45:30 -0700, wxjmfauth wrote:
Sorry guys, I'm only able to see this (with the Python versions an end
user can download):
[snip timeit results]
While you have been all doom and gloom and negativity that Python has
destroyed Unicode, I've actually done some testing. It
Hi
Sorry guys, I'm only able to see this (with the Python versions an end
user can download):
[snip timeit results]
While you have been all doom and gloom and negativity that Python has
destroyed Unicode,
I thought that jmf's concerns were solely concerned with the selection
of latin1 as
On Thu, Sep 27, 2012 at 2:13 AM, Steven D'Aprano
steve+comp.lang.pyt...@pearwood.info wrote:
On Tue, 25 Sep 2012 09:15:00 +0100, Mark Lawrence wrote:
And a response:
http://data.geek.nz/python-is-doing-just-fine
Summary of that article:
Sure, you have all these legitimate concerns, but look,
On 27.09.12 12:33, Steven D'Aprano wrote:
Nevertheless, I think there is something here. The consequences are nowhere
near as dramatic as jmf claims, but it does seem that replace() has taken a
serious performance hit. Perhaps it is unavoidable, but perhaps not.
If anyone else can confirm
On 2012-09-27, Chris Angelico ros...@gmail.com wrote:
On Thu, Sep 27, 2012 at 4:01 PM, Steven D'Aprano
steve+comp.lang.pyt...@pearwood.info wrote:
Given how Perl has slipped in the last decade or so, that would be a step
backwards for Python :-P
LAMP usually means PHP these days. There's a
On Thu, 27 Sep 2012 08:11:13 -0400, Devin Jeanpierre wrote:
On Thu, Sep 27, 2012 at 2:13 AM, Steven D'Aprano
steve+comp.lang.pyt...@pearwood.info wrote:
On Tue, 25 Sep 2012 09:15:00 +0100, Mark Lawrence wrote: And a
response:
http://data.geek.nz/python-is-doing-just-fine
Summary of that
On Thu, Sep 27, 2012 at 11:59 PM, Grant Edwards invalid@invalid.invalid wrote:
On 2012-09-27, Chris Angelico ros...@gmail.com wrote:
On Thu, Sep 27, 2012 at 4:01 PM, Steven D'Aprano
steve+comp.lang.pyt...@pearwood.info wrote:
Given how Perl has slipped in the last decade or so, that would be
On Thu, Sep 27, 2012 at 4:43 AM, Alex Strickland s...@mweb.co.za wrote:
I thought that jmf's concerns were solely concerned with the selection of
latin1 as the 1 byte set. My impression was that if some set of characters
was chosen that included all characters commonly used in French then all
On 27/09/2012 13:46, Serhiy Storchaka wrote:
On 27.09.12 12:33, Steven D'Aprano wrote:
Nevertheless, I think there is something here. The consequences are
nowhere
near as dramatic as jmf claims, but it does seem that replace() has
taken a
serious performance hit. Perhaps it is unavoidable, but
On Thu, Sep 27, 2012 at 10:25 AM, Steven D'Aprano
steve+comp.lang.pyt...@pearwood.info wrote:
On Thu, 27 Sep 2012 08:11:13 -0400, Devin Jeanpierre wrote:
On Thu, Sep 27, 2012 at 2:13 AM, Steven D'Aprano
steve+comp.lang.pyt...@pearwood.info wrote:
On Tue, 25 Sep 2012 09:15:00 +0100, Mark
On 27/09/2012 17:16, Devin Jeanpierre wrote:
On Thu, Sep 27, 2012 at 10:25 AM, Steven D'Aprano
steve+comp.lang.pyt...@pearwood.info wrote:
On Thu, 27 Sep 2012 08:11:13 -0400, Devin Jeanpierre wrote:
On Thu, Sep 27, 2012 at 2:13 AM, Steven D'Aprano
steve+comp.lang.pyt...@pearwood.info wrote:
On 27/09/2012 07:13, Steven D'Aprano wrote:
On Tue, 25 Sep 2012 09:15:00 +0100, Mark Lawrence wrote:
Hi all,
I though this might be of interest.
http://www.ironfroggy.com/software/i-am-worried-about-the-future-of-
python
And a response:
http://data.geek.nz/python-is-doing-just-fine
On Fri, Sep 28, 2012 at 2:45 AM, Mark Lawrence breamore...@yahoo.co.uk wrote:
The article Steven D'Aprano referred to is not a direct response to the
article I referred to, yet your words are written as if it were. May I ask
why? Or have I missed something?
Steven cited it with the words And
On Thu, Sep 27, 2012 at 12:45 PM, Mark Lawrence breamore...@yahoo.co.uk wrote:
The article Steven D'Aprano referred to is not a direct response to the
article I referred to, yet your words are written as if it were. May I ask
why? Or have I missed something?
Post hoc ergo propter hoc :(
--
On 27/09/2012 17:49, Chris Angelico wrote:
On Fri, Sep 28, 2012 at 2:45 AM, Mark Lawrence breamore...@yahoo.co.uk wrote:
The article Steven D'Aprano referred to is not a direct response to the
article I referred to, yet your words are written as if it were. May I ask
why? Or have I missed
Mark Lawrence wrote:
On 27/09/2012 17:16, Devin Jeanpierre wrote:
On Thu, Sep 27, 2012 at 10:25 AM, Steven D'Aprano wrote:
On Thu, 27 Sep 2012 08:11:13 -0400, Devin Jeanpierre wrote:
Summary of that article:
Sure, you have all these legitimate concerns, but look, cake!
Did you read the
On 27.09.12 18:06, Ian Kelly wrote:
I understand ISO 8859-15 (Latin-9) to be the preferred Latin character
set for French, as it includes the Euro sign as well as a few
characters that are not in Latin-1 but are nonetheless infrequently
found in French.
Even for Latin-9 Python 3.3 can be a
On 9/27/2012 5:33 AM, Steven D'Aprano wrote:
Nevertheless, I think there is something here. The consequences are nowhere
near as dramatic as jmf claims, but it does seem that replace() has taken a
serious performance hit. Perhaps it is unavoidable, but perhaps not.
If anyone else can confirm
This flexible string representation is wrong by design.
Expecting to divide Unicode in chunks and to gain something
is an illusion.
It has been created by a computer scientist who thinks bytes
when on that field one has to think bytes and usage of the
characters at the same time.
The latin-1 chunk
On 9/27/2012 12:16 PM, Devin Jeanpierre wrote:
Charitably, maybe we'd call this a way of encouraging people who are
discouraged by the bleaker tone of Calvin's post. And that's valid, if
we're worried about morale. Definitely Calvin's post could be -- and
has been -- taken the wrong way. It
On 27/09/2012 20:09, wxjmfa...@gmail.com wrote:
This flexible string representation is wrong by design.
Please state who agrees with this and why.
Expecting to divide Unicode in chunks and to gain something
is an illusion.
Please provide the benchmarks to support your claim.
It has been
You're posting to both comp.lang.python and python-list, are you aware
that that's redundant?
On Fri, Sep 28, 2012 at 5:09 AM, wxjmfa...@gmail.com wrote:
This flexible string representation is wrong by design.
Expecting to divide Unicode in chunks and to gain something
is an illusion.
It has
On Sep 28, 2:47 am, Mark Lawrence breamore...@yahoo.co.uk wrote:
... why does the runtime environment have to be so limiting? Operations
involving primitives could be easily compiled (on the fly - JIT) to
machine code and more advanced objects exist as plug-ins. Oh, and it
would be nice to be
On Sep 28, 2:17 am, Devin Jeanpierre jeanpierr...@gmail.com wrote:
Uncharitably, it's just a way of hiding one's head in the sand,
ignoring any problems Python has by focusing on what problems it
doesn't have.
But isn't that what counterpoint is all about? Calvin's article
highlighted what he
On Fri, 28 Sep 2012 00:32:58 +1000, Chris Angelico wrote:
On Thu, Sep 27, 2012 at 11:59 PM, Grant Edwards
invalid@invalid.invalid wrote:
On 2012-09-27, Chris Angelico ros...@gmail.com wrote:
On Thu, Sep 27, 2012 at 4:01 PM, Steven D'Aprano
steve+comp.lang.pyt...@pearwood.info wrote:
Given
Fair enough, but it's the M in the LAMP stack I object to. I'd much
rather have P.
+1
--
http://mail.python.org/mailman/listinfo/python-list
On 9/27/2012 9:05 PM, Jason Friedman wrote:
Fair enough, but it's the M in the LAMP stack I object to. I'd much
rather have P.
+1
I know this isn't the list for database discussions, but I've never
gotten a decent answer. I don't know much about either, so I'm kind of
curious why
On 9/27/2012 9:05 PM, Jason Friedman wrote:
Fair enough, but it's the M in the LAMP stack I object to. I'd much
rather have P.
+1
I know this isn't the list for database discussions, but I've never gotten a
decent answer. I don't know much about either, so I'm kind of curious why
On Thu, Sep 27, 2012 at 10:14 PM, Littlefield, Tyler
ty...@tysdomain.com wrote:
I know this isn't the list for database discussions, but I've never gotten a
decent answer. I don't know much about either, so I'm kind of curious why
postgresql over mysql?
MySQL is an open-source PRODUCT owned by
On Thu, Sep 27, 2012 at 10:37 PM, Wayne Werner wa...@waynewerner.com wrote:
the only advice I can give on that is
just learn to use both.
I find there's little to lose in having experience with both.
Most every good web framework out there supports lots of different
databases through generic
On Fri, Sep 28, 2012 at 2:12 PM, Greg Donald gdon...@gmail.com wrote:
On Thu, Sep 27, 2012 at 10:37 PM, Wayne Werner wa...@waynewerner.com wrote:
the only advice I can give on that is
just learn to use both.
I find there's little to lose in having experience with both.
Most every good web
On 9/27/2012 10:37 PM, Chris Angelico wrote:
On Fri, Sep 28, 2012 at 2:12 PM, Greg Donald gdon...@gmail.com wrote:
On Thu, Sep 27, 2012 at 10:37 PM, Wayne Werner wa...@waynewerner.com wrote:
the only advice I can give on that is
just learn to use both.
I find there's little to lose in having
On Wed, Sep 26, 2012 at 3:16 PM, Steven D'Aprano
steve+comp.lang.pyt...@pearwood.info wrote:
On Wed, 26 Sep 2012 14:10:28 +1000, Chris Angelico wrote:
The flip side to node.js is pyjs.
After the ham-fisted, nasty way pyjamas project was hijacked this year,
I'm not entirely sure I'd want to
Chris Angelico ros...@gmail.com writes:
That is true, but the concept is still around - that you can write
your code in some other language and compile to js.
http://www.haskell.org/haskellwiki/The_JavaScript_Problem
--
http://mail.python.org/mailman/listinfo/python-list
Le mercredi 26 septembre 2012 01:34:01 UTC+2, 8 Dihedral a écrit :
Grant Edwards於 2012年9月26日星期三UTC+8上午2時25分31秒寫道：
On 2012-09-25, Martin P. Hellwig martin.hell...@gmail.com wrote:
On Tuesday, 25 September 2012 09:14:27 UTC+1, Mark Lawrence wrote:
Hi all,
On Tue, 25 Sep 2012 23:35:39 -0700, wxjmfauth wrote:
Py 3.3 succeeded to somehow kill unicode and it has been transformed
into an American product for American users.
For the first time in Python's history, Python on 32-bit systems handles
strings containing Supplementary Multilingual Plane
wxjmfa...@gmail.com wrote:
Py 3.3 succeeded to somehow kill unicode and it has
been transformed into an American product for
American users.
*plonk*
--
http://mail.python.org/mailman/listinfo/python-list
On Wed, Sep 26, 2012 at 3:17 AM, Ethan Furman et...@stoneleaf.us wrote:
wxjmfa...@gmail.com wrote:
Py 3.3 succeeded to somehow kill unicode and it has
been transformed into an American product for
American users.
Well, we can all use american as a standard, or maybe you'd prefer to
borrow
On Wed, Sep 26, 2012 at 5:39 PM, Dwight Hutto dwightdhu...@gmail.com wrote:
On Wed, Sep 26, 2012 at 3:17 AM, Ethan Furman et...@stoneleaf.us wrote:
wxjmfa...@gmail.com wrote:
Py 3.3 succeeded to somehow kill unicode and it has
been transformed into an American product for
American users.
Well, we can all use american as a standard, or maybe you'd prefer to
borrow my Latin for Idiots handbook. But then again google has a
Universal Communicator going, so, does it matter?
Never in the field of human discussion has there been so much reason
for so many to plonk so few.
Plonk it
On 9/26/2012 2:35 AM, wxjmfa...@gmail.com wrote:
Py 3.3 succeeded to somehow kill unicode and it has
been transformed into an American product for
American users.
Python 3.3 is the first version that handles the full unicode character
set correctly on all platforms. If anything, it will make
On 26/09/2012 05:10, Chris Angelico wrote:
On Wed, Sep 26, 2012 at 10:54 AM, Steven D'Aprano
steve+comp.lang.pyt...@pearwood.info wrote:
SQL? ... it's time to sell your shares in Oracle.
Ehh, I wouldn't be investing in Oracle, but that's more because I
think free RDBMSes like PostgreSQL
On 26/09/2012 07:35, wxjmfa...@gmail.com wrote:
Py 3.3 succeeded to somehow kill unicode and it has
been transformed into an American product for
American users.
jmf
Why do you keep repeating this rubbish when you've already been shot to
pieces? Don't you know when it's time to make sure
On 26/09/2012 08:44, Chris Angelico wrote:
On Wed, Sep 26, 2012 at 5:39 PM, Dwight Hutto dwightdhu...@gmail.com wrote:
On Wed, Sep 26, 2012 at 3:17 AM, Ethan Furman et...@stoneleaf.us wrote:
wxjmfa...@gmail.com wrote:
Py 3.3 succeeded to somehow kill unicode and it has
been transformed into
On Wed, Sep 26, 2012 at 6:34 PM, Mark Lawrence breamore...@yahoo.co.uk wrote:
Further for somebody who is apparently up in the high tech world, why are
you using a gmail account and hence sending garbage in more ways than one to
mailing lists like this?
I use gmail too, largely because I
Why do you keep repeating this rubbish when you've already been shot to
pieces?
I still feel intact, so whatever little shards of pain you intended to
emit were lost on my ego.
Don't you know when it's time to make sure that you're safely
strapped in and reach for and use the release
I tried to make a play on that some days ago and failed dismally.
That's the fucking understatement of the year.
Thanks for
putting me out of my misery :)
--
No prob.
Best Regards,
David Hutto
CEO: http://www.hitwebdevelopment.com
--
http://mail.python.org/mailman/listinfo/python-list
On 26/09/2012 09:47, Dwight Hutto wrote:
I tried to make a play on that some days ago and failed dismally.
That's the fucking understatement of the year.
You remind me of the opening to the song Plaistow Patricia by Ian Dury
and the Blockheads.
Thanks for
putting me out of my misery
That's the fucking understatement of the year.
You remind me of the opening to the song Plaistow Patricia by Ian Dury and
the Blockheads.
Make a modern day/mainstream reference, and maybe someone will get it.
Thanks for
putting me out of my misery :)
Again, no problem...anytime
-the-future-of-
python
Interesting article, but the comments of those who say the only
language I need to know is Python strike me as a bit limited. If this
is the case, then Python can never be moved forward, because it is
written in C.
Incorrect.
IronPython
Le mercredi 26 septembre 2012 09:23:47 UTC+2, Steven D'Aprano a écrit :
On Tue, 25 Sep 2012 23:35:39 -0700, wxjmfauth wrote:
Py 3.3 succeeded to somehow kill unicode and it has been transformed
into an American product for American users.
Steven,
you are correct. But the price
they are written in themselves, using some clever bootstrapping
techniques. C is neither the most powerful, the oldest, the best, or the
most fundamental language around.
Would you recommend Assembly, because C just becomea macros of
Assembly, or better yet machine language, which is line
On Wed, Sep 26, 2012 at 7:31 PM, wxjmfa...@gmail.com wrote:
you are correct. But the price you pay for this is extremely
high. Now, practically all characters are affected, espacially
those *in* the Basic *** Multilingual*** Plane, these characters
used by non American user (No offense here,
On 09/26/2012 10:32 AM, Mark Lawrence wrote:
On 26/09/2012 05:10, Chris Angelico wrote:
On Wed, Sep 26, 2012 at 10:54 AM, Steven D'Aprano
steve+comp.lang.pyt...@pearwood.info wrote:
SQL? ... it's time to sell your shares in Oracle.
Ehh, I wouldn't be investing in Oracle, but that's more
Le mercredi 26 septembre 2012 10:35:04 UTC+2, Mark Lawrence a écrit :
On 26/09/2012 07:35, wxjmfa...@gmail.com wrote:
Py 3.3 succeeded to somehow kill unicode and it has
been transformed into an American product for
American users.
jmf
Why do you keep repeating this
Le mercredi 26 septembre 2012 10:13:58 UTC+2, Terry Reedy a écrit :
On 9/26/2012 2:35 AM, wxjmfa...@gmail.com wrote:
Py 3.3 succeeded to somehow kill unicode and it has
been transformed into an American product for
American users.
Python 3.3 is the first version that
In article mailman.1421.1348653712.27098.python-l...@python.org,
Hannu Krosing ha...@krosing.net wrote:
You can get only so far using sales. At some point you have to deliver.
But, by that time, the guy who closed the sale has already cashed his
bonus check, bought his new BMW, and moved on
On 26/09/2012 10:31, wxjmfa...@gmail.com wrote:
I'm ready to be considered as an idiot, but I'm not blind.
People here have seen enough of your writings to know that you're not an
idiot. I'm feeling far too polite right now to state what they actually
know about you.
As soon as I
On 26/09/2012 14:01, Roy Smith wrote:
In article mailman.1421.1348653712.27098.python-l...@python.org,
Hannu Krosing ha...@krosing.net wrote:
You can get only so far using sales. At some point you have to deliver.
But, by that time, the guy who closed the sale has already cashed his
bonus
On 9/26/2012 2:11 AM, Dwight Hutto wrote:
Well, we can all use american as a standard, or maybe you'd prefer to
borrow my Latin for Idiots handbook. But then again google has a
Universal Communicator going, so, does it matter?
Never in the field of human discussion has there been so much reason
On 9/25/12 11:35 AM, Steven D'Aprano wrote:
IronPython in C#. Jython is written in Java. CLPython is written in Lisp.
Berp and HoPe are written in Haskell. Nuitka is written in C++. Skulpt is
written in Javascript. Vyper is written in Ocaml. PyPy is written in
RPython.
Some of those Python
On 26/09/2012 14:31, Littlefield, Tyler wrote:
PS: Anyone know if rantingrik had relatives? ;)
I say steady on old chap that's just not cricket. I've been known to
have a go at rr in the past for good reasons, but when he gets stuck
into Tkinter he is an extremely useful contributor. I
On Wed, Sep 26, 2012 at 10:19 PM, wxjmfa...@gmail.com wrote:
You are always selling the same argument.
Py3.3 is the only computer language I'm aware of which
is maltreating Unicode in such a way.
You mean, the only computer language that represents Unicode
characters as integers, and then
On Wed, Sep 26, 2012 at 11:43 PM, Mark Lawrence breamore...@yahoo.co.uk wrote:
On 26/09/2012 14:31, Littlefield, Tyler wrote:
PS: Anyone know if rantingrik had relatives? ;)
I say steady on old chap that's just not cricket. I've been known to have a
go at rr in the past for good reasons,
Le mercredi 26 septembre 2012 11:55:16 UTC+2, Chris Angelico a écrit :
On Wed, Sep 26, 2012 at 7:31 PM, wxjmfa...@gmail.com wrote:
you are correct. But the price you pay for this is extremely
high. Now, practically all characters are affected, espacially
those *in* the Basic ***
On Thu, Sep 27, 2012 at 12:19 AM, wxjmfa...@gmail.com wrote:
No, I'm comparing Py33 with Py32 narrow build [*].
Then look at the broken behaviour that Python, up until now, shared
with Javascript and various other languages, in which a one-character
string appears as two characters, and slicing
I should add that I have not the knowledge to dive
in the Python code. But I see what has been done.
As I have a very good understanding of all this
coding of characters stuff, I can just pick up
- in fact select characters or combination
of characters - which I supspect to be problematic
and I
On Thu, Sep 27, 2012 at 12:50 AM, wxjmfa...@gmail.com wrote:
I just see the results and the facts. For an end
user, this is the only thing that counts.
Then what counts is that Python 3.2 (like Javascript) exhibits
incorrect behaviour, and Python (like Pike) performs correctly.
I think this
On 26/09/2012 15:50, wxjmfa...@gmail.com wrote:
I should add that I have not the knowledge to dive
in the Python code. But I see what has been done.
How?
As I have a very good understanding of all this
coding of characters stuff, I can just pick up
- in fact select characters or combination
Le mercredi 26 septembre 2012 16:56:55 UTC+2, Chris Angelico a écrit :
On Thu, Sep 27, 2012 at 12:50 AM, wxjmfa...@gmail.com wrote:
I just see the results and the facts. For an end
user, this is the only thing that counts.
Then what counts is that Python 3.2 (like Javascript)
Sorry guys, I'm only able to see this
(with the Python versions an end user can
download):
timeit.repeat(('你'*1).replace('你', 'a'))
[31.44532887821319, 31.409585124813844, 31.40705548932476]
timeit.repeat(('你'*1).replace('你', 'a'))
[323.56687741054805, 323.1660997337247,
On Wed, Sep 26, 2012 at 1:23 AM, Steven D'Aprano
steve+comp.lang.pyt...@pearwood.info wrote:
On Tue, 25 Sep 2012 23:35:39 -0700, wxjmfauth wrote:
Py 3.3 succeeded to somehow kill unicode and it has been transformed
into an American product for American users.
For the first time in Python's
Mark Lawrence wrote:
On 26/09/2012 14:31, Littlefield, Tyler wrote:
PS: Anyone know if rantingrik had relatives? ;)
I say steady on old chap that's just not cricket. I've been known to
have a go at rr in the past for good reasons, but when he gets stuck
into Tkinter he is an extremely
Le mercredi 26 septembre 2012 17:54:04 UTC+2, Ian a écrit :
On Wed, Sep 26, 2012 at 1:23 AM, Steven D'Aprano
steve+comp.lang.pyt...@pearwood.info wrote:
On Tue, 25 Sep 2012 23:35:39 -0700, wxjmfauth wrote:
Py 3.3 succeeded to somehow kill unicode and it has been transformed
Chris Angelico wrote:
On Wed, Sep 26, 2012 at 10:19 PM, wxjmfa...@gmail.com wrote:
After all, if replacing a Nabla operator in a string take
10 times more times in Py33 than in Python32 [. . .]
But I'll give you the benefit
of the doubt; maybe your number is in binary.
+1 QOTW
--
Chris Angelico ros...@gmail.com writes:
When you compare against a wide build, semantics of 3.2 and 3.3 are
identical, and then - and ONLY then - can you sanely compare
performance. And 3.3 stacks up much better.
I like to have seen real world benchmarks against a pure UTF-8
implementation.
On Thu, Sep 27, 2012 at 2:52 AM, Paul Rubin no.email@nospam.invalid wrote:
Chris Angelico ros...@gmail.com writes:
When you compare against a wide build, semantics of 3.2 and 3.3 are
identical, and then - and ONLY then - can you sanely compare
performance. And 3.3 stacks up much better.
I
Chris Angelico ros...@gmail.com writes:
So, I don't actually have any stats for you, because it's really easy
to just not index strings at all.
Right, that's why I think the O(n) indexing issue of UTF-8 may be
overblown. Haskell 98 was mentioned earlier as a language that did
Unicode
Le mercredi 26 septembre 2012 18:52:44 UTC+2, Paul Rubin a écrit :
Chris Angelico ros...@gmail.com writes:
When you compare against a wide build, semantics of 3.2 and 3.3 are
identical, and then - and ONLY then - can you sanely compare
performance. And 3.3 stacks up much better.
Resending to the list.
-- Forwarded message --
From: Ian Kelly ian.g.ke...@gmail.com
Date: Sep 26, 2012 12:57 PM
Subject: Re: Article on the future of Python
To: wxjmfa...@gmail.com
On Sep 26, 2012 12:42 AM, wxjmfa...@gmail.com wrote:
Py 3.3 succeeded to somehow kill unicode
On 9/26/2012 4:45 AM, Dwight Hutto wrote:
Why do you keep repeating this rubbish when you've already been shot to
pieces?
I still feel intact, so whatever little shards of pain you intended to
emit were lost on my ego.
Uh, Dwight, he was not talking to you.
--
Terry Jan Reedy
--
On 26/09/12 15:30, Kevin Walzer wrote:
Apart from IronPython, what constituency do these alternative
and Jython ... that is widely used in the Java server world
implementations of Python have that would raise them above the level of
interesting experiments?
Matěj
--
On 9/26/2012 8:19 AM, wxjmfa...@gmail.com wrote:
You are always selling the same argument.
Because you keep repeating the same insane argument against 3.3.
Py3.3 is the only computer language I'm aware of which
is maltreating Unicode in such a way.
You have it backwards. 3.3 fixes
On 9/26/2012 2:58 PM, Ian Kelly wrote:
You know, usually when I see software decried as America-centric, it's
because it doesn't support Unicode. This must be the first time I've
seen that label applied to software that dares to *fully* support Unicode.
What is truly bizarre is the idea came
1 - 100 of 119 matches
Mail list logo
