On Thu, 16 Dec 2004 06:13:41 -0700, Stewart Midwinter
<[EMAIL PROTECTED]> wrote:
> [...] Possible slogan for Python: "Fast enough, and better in many ways".
> [...]
Let's make it faster first :-)
Cheers,
Michael
___
Python-Dev mailing list
[EMAIL PROTEC
A number of people commented on the article in GCN, at
http://gcn.com/vol1_no1/daily-updates/28026-1.html, and wondered if
more could not be done to address the perception of speed. The point
is made that although people mention all of the benefits of Python,
like ease of use, flexibility, they alw
On Dec 15, 2004, at 2:58 PM, Terry Reedy wrote:
Your primary choice is whether to work on changes in the C code for the
interpreter and builtin modules or changes in the Python code in
standard
library modules.
The PyPy folks might be useful too given that they are writing Python
in Python.
http
If this still occurs with Python 2.3.4 or 2.4, please file a bug so it
can be fixed (python-dev isn't a good place to remember fixes).
On Thu, 16 Dec 2004 14:03:55 +0100, Eirik Mikkelsen
<[EMAIL PROTECTED]> wrote:
> On Thu, 2004-12-16 at 12:30 +, Johan Carlstedt wrote:
> > Hello,
> >
> > I am
On Thu, 2004-12-16 at 12:30 +, Johan Carlstedt wrote:
> Hello,
>
> I am having problems compiling Python 2.3.3 on Solaris 10 X86 using gcc
> 3.4.1. The error message below is generated.
>
[SNIP]
> Objects/complexobject.c
> Objects/complexobject.c: In function `complex_pow':
> Objects/complexo
Hello,
I am having problems compiling Python 2.3.3 on Solaris 10 X86 using gcc
3.4.1. The error message below is generated.
I would be grateful for any advice.
With friendly regards,
Johan Carlstedt
# make
gcc -c -fno-strict-aliasing -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -I. -
I./Include
