Guido van Rossum wrote:
I was pleasantly surprised to find a pointer to this article in a news
digest that the ACM emails me regularly (ACM TechNews).
http://gcn.com/vol1_no1/daily-updates/28026-1.html
One thing that bugs me: the article says 3 or 4 times that Python is
slow, each time with a refut
On Wed, Dec 08, 2004 at 02:18:48PM -0800, Guido van Rossum wrote:
> I was pleasantly surprised to find a pointer to this article in a news
> digest that the ACM emails me regularly (ACM TechNews).
>
> http://gcn.com/vol1_no1/daily-updates/28026-1.html
>
> One thing that bugs me: the article says
[ Guido van Rossum <[EMAIL PROTECTED]> ]
---
| One thing that bugs me: the article says 3 or 4 times that Python is
| slow, each time with a refutation ("but it's so flexible", "but it's
| fast enough") but still, they sure seem to harp on the point.
On Tue, 14 Dec 2004 01:05:09 -0200, Rodrigo Dias Arruda Senra
<[EMAIL PROTECTED]> wrote:
> But, but to the joke: I believe Python must strive to run at least as fast as
> the crowd --
> Java, Perl, Ruby, Lua, Boo, etc
>
> Maybe we could visit the language shootout sites, translate Python snipets
On Wed, 8 Dec 2004, Phillip J. Eby wrote:
> At 02:18 PM 12/8/04 -0800, Guido van Rossum wrote:
> >I was pleasantly surprised to find a pointer to this article in a news
> >digest that the ACM emails me regularly (ACM TechNews).
> >
> >http://gcn.com/vol1_no1/daily-updates/28026-1.html
> >
> >One t
On Wed, 8 Dec 2004, Raymond Hettinger wrote:
> > One thing that bugs me: the article says 3 or 4 times that Python is
> > slow, each time with a refutation ("but it's so flexible", "but it's
> > fast enough") but still, they sure seem to harp on the point. This is
> > a PR issue that Python needs
Hi Skip,
On Fri, Dec 10, 2004 at 04:49:30AM -0600, Skip Montanaro wrote:
>
> >> The other thing we can do is finish the portable backend for psyco
> >> and make it a standard module. Then Python won't be slow, it will be
> >> compiled, and py2exe will be able to make a single-file ex
Thomas> I haven't tried it, but using psyco in a script and building an
Thomas> exe from it with py2exe should work right out of the box - but
Thomas> maybe this isn't what you had in mind?
I was thinking of implicitly mixing in psyco, even if the script didn't use
it. Maybe I have t
Jeremy Hylton <[EMAIL PROTECTED]> writes:
> I agree, although it's not clear to me how much faster it will be in
> the future. Making a *fast* Python based on our own virtual execution
> environment (as opposed to piggybacking a JVM or CLR) is a big
> project. It's not clear than anyone has enou
Skip Montanaro <[EMAIL PROTECTED]> writes:
> >> The other thing we can do is finish the portable backend for psyco
> >> and make it a standard module. Then Python won't be slow, it will be
> >> compiled, and py2exe will be able to make a single-file executable.
>
> Armin> You prob
>> The other thing we can do is finish the portable backend for psyco
>> and make it a standard module. Then Python won't be slow, it will be
>> compiled, and py2exe will be able to make a single-file executable.
Armin> You probably mean that Psyco can dynamically compile Python
Hi Andrew,
On Thu, Dec 09, 2004 at 03:32:10PM +1300, Andrew McGregor wrote:
> The other thing we can do is finish the portable backend for psyco and
> make it a standard module. Then Python won't be slow, it will be
> compiled, and py2exe will be able to make a single-file executable.
You pr
Raymond> * Any PR effort should also emphasize that no usability
Raymond> trade-offs were made along the way. A number of features
Raymond> make Py2.4 easier to use than 1.5.6: list comps, genexps,
Raymond> generators, sets, nested scopes, int/long unification,
Raymond>
Guido van Rossum wrote:
[snip]
One thing that bugs me: the article says 3 or 4 times that Python is
slow, each time with a refutation ("but it's so flexible", "but it's
fast enough") but still, they sure seem to harp on the point. This is
a PR issue that Python needs to fight -- any ideas?
One thin
On Thu, 2004-12-09 at 16:37 -0500, Phillip J. Eby wrote:
> +1 on all the stuff you said, with one minor exception. Pyrex-the-language
> is often unpythonically ugly and verbose at present.
Personally I have no problem with Pyrex's current tradeoffs, but given
the amount of effort that this is g
If I parse you correctly, this would be great.
- Michael
On Thu, 09 Dec 2004 16:37:59 -0500, Phillip J. Eby
<[EMAIL PROTECTED]> wrote:
> At 04:11 PM 12/9/04 -0500, Glyph Lefkowitz wrote:
>
>
> >On Wed, 2004-12-08 at 17:39 -0500, Phillip J. Eby wrote:
> >
> > > The only thing that will fix the
At 04:11 PM 12/9/04 -0500, Glyph Lefkowitz wrote:
On Wed, 2004-12-08 at 17:39 -0500, Phillip J. Eby wrote:
> The only thing that will fix the PR issue is to have a Python compiler
> distributed as part of the language. It doesn't matter if it doesn't
> support the full generality of Python, or eve
On Dec 9, 2004, at 4:20 PM, Barry Warsaw wrote:
On Thu, 2004-12-09 at 10:30, Phillip J. Eby wrote:
ISTR that for a long time, Visual Basic actually did the same thing.
A few
magazines mentioned the fact, but nobody really cared. However, if
this is
really a concern, bundle Pyrex as well. Both
On Thu, 2004-12-09 at 10:30, Phillip J. Eby wrote:
> ISTR that for a long time, Visual Basic actually did the same thing. A few
> magazines mentioned the fact, but nobody really cared. However, if this is
> really a concern, bundle Pyrex as well. Both Pyrex and py2exe are
> distutils-based,
On Wed, 2004-12-08 at 17:39 -0500, Phillip J. Eby wrote:
> The only thing that will fix the PR issue is to have a Python compiler
> distributed as part of the language. It doesn't matter if it doesn't
> support the full generality of Python, or even if it doesn't speed many
> operations up muc
On Thu, 9 Dec 2004 14:16:18 -0500, James Y Knight <[EMAIL PROTECTED]> wrote:
> On Dec 9, 2004, at 1:31 PM, Phillip J. Eby wrote:
> > Isn't it funny, by the way, that people don't go around talking about
> > how slow Jython is? At least, I haven't seen it to the extent that
> > I've seen with CPyth
On Dec 9, 2004, at 1:31 PM, Phillip J. Eby wrote:
Isn't it funny, by the way, that people don't go around talking about
how slow Jython is? At least, I haven't seen it to the extent that
I've seen with CPython.
People talk about how slow CPython is, is because they are writing code
targeted for
At 04:39 PM 12/9/04 +, Gareth McCaughan wrote:
On Wednesday 2004-12-08 22:39, Phillip J. Eby wrote:
> The only thing that will fix the PR issue is to have a Python compiler
> distributed as part of the language. It doesn't matter if it doesn't
> support the full generality of Python, or even i
> The other thing that might work is to change the name of the language
> to "C" plus optional punctuation.
You mean "C@@" (pronounced C-pie-pie)?
Bill
___
Python-Dev mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/python-dev
Unsu
On Wednesday 2004-12-08 22:39, Phillip J. Eby wrote:
[Guido:]
>> One thing that bugs me: the article says 3 or 4 times that Python is
>> slow, each time with a refutation ("but it's so flexible", "but it's
>> fast enough") but still, they sure seem to harp on the point. This is
>> a PR issue that
At 01:17 PM 12/9/04 +0300, Oleg Broytmann wrote:
On Wed, Dec 08, 2004 at 08:30:02PM -0500, Phillip J. Eby wrote:
> As I explained later in that message, "native" simply means, "has an .exe
> extension on Windows".
And very soon that strategy will backfire - people will start PRing
"but those .ex
On Thursday 09 December 2004 14:55, Raymond Hettinger wrote:
> * Have python.org prominently feature an article of Python's use in
> high-performance environments. IIRC, somebody wrote a realtime voice
> over internet system and found that with good design, there was no speed
> issue. Also, the c
On Wed, Dec 08, 2004 at 10:55:59PM -0500, Raymond Hettinger wrote:
> * Have python.org prominently feature an article of Python's use in
> high-performance environments. IIRC, somebody wrote a realtime voice
> over internet system and found that with good design, there was no speed
> issue. Also,
On Wed, Dec 08, 2004 at 08:30:02PM -0500, Phillip J. Eby wrote:
> As I explained later in that message, "native" simply means, "has an .exe
> extension on Windows".
And very soon that strategy will backfire - people will start PRing
"but those .exe's are nothing more than a python interpreter
> One thing that bugs me: the article says 3 or 4 times that Python is
> slow, each time with a refutation ("but it's so flexible", "but it's
> fast enough") but still, they sure seem to harp on the point. This is
> a PR issue that Python needs to fight -- any ideas?
* Ask a prominent PSF member,
On Wed, 8 Dec 2004, Guido van Rossum wrote:
> One thing that bugs me: the article says 3 or 4 times that Python is
> slow, each time with a refutation ("but it's so flexible", "but it's
> fast enough") but still, they sure seem to harp on the point. This is
> a PR issue that Python needs to figh
Well, for a lot of applications for Python, the performance that really
counts is time from no code but a pile of data to code and processed
data. Python shines at that because nearly always the time to write
the code dominates, so it doesn't matter what the run time is.
I wrote a little to
At 01:25 AM 12/9/04 +0200, Stelios Xanthakis wrote:
The only thing that will fix the PR issue is to have a Python compiler
distributed as part of the language. It doesn't matter if it doesn't
support the full generality of Python, or even if it doesn't speed many
operations up much. The only rea
[Guido van Rossum Wed, Dec 08, 2004 at 02:18:48PM -0800]
> I was pleasantly surprised to find a pointer to this article in a news
> digest that the ACM emails me regularly (ACM TechNews).
>
> http://gcn.com/vol1_no1/daily-updates/28026-1.html
>
> One thing that bugs me: the article says 3 or 4 ti
On Wed, Dec 08, 2004 at 02:18:48PM -0800, Guido van Rossum wrote:
> This is a PR issue that Python needs to fight -- any ideas?
I'm not good at PR so I will continue to try to make it faster. In
my copious free time I plan to:
* finish the AST compiler (no performance benefit but makes
The only thing that will fix the PR issue is to have a Python compiler
distributed as part of the language. It doesn't matter if it doesn't
support the full generality of Python, or even if it doesn't speed many
operations up much. The only real requirements are that it can be used
to produce "
Guido van Rossum wrote:
I was pleasantly surprised to find a pointer to this article in a news
digest that the ACM emails me regularly (ACM TechNews).
http://gcn.com/vol1_no1/daily-updates/28026-1.html
One thing that bugs me: the article says 3 or 4 times that Python is
slow, each time with a refut
At 02:18 PM 12/8/04 -0800, Guido van Rossum wrote:
I was pleasantly surprised to find a pointer to this article in a news
digest that the ACM emails me regularly (ACM TechNews).
http://gcn.com/vol1_no1/daily-updates/28026-1.html
One thing that bugs me: the article says 3 or 4 times that Python is
s
38 matches
Mail list logo
