This is great news. Congratulations!
By the way, I read in your blog that you would be releasing a windows
intaller soon.
Have you, or anyone else, managed to do it?
Cheers,
Luis
--
http://mail.python.org/mailman/listinfo/python-list
Mark Dufour wrote:
In general it's considered quite pythonic to catch exceptions :-)
It's a particularly useful way of implementing duck typing for example.
I'm not sure if I've got *any* code that doesn't use exceptions
somewhere
Hehe. Okay. It will probably always be the case that you
Hehe. Okay. It will probably always be the case that you have to lose
some Python features if you want the code to run really fast. I
suppose PyPy's restricted Python subset doesn't support duck typing
either. Luckily not all code is performance critical, or you could
just try and optimize
Mark Dufour wrote:
You're right, I don't feel safe about that. It's a bad example. I just
prefer error codes, because the code usually becomes cleaner (at least
to me). I would really like it if I could do something like this:
f = file(name)
if not f:
print 'error opening file %s:
You forgot to check for an error when:
o when you wrote f.error [attribute error might not exist e.g. f is
None]
o you called str(f.error) [might contain unicode characters that can't
be converted to a string using the default
Mark Dufour wrote:
[Brian Quinlan wrote:]
You forgot to check for an error when:
o when you wrote f.error [attribute error might not exist e.g. f is
None]
o you called str(f.error) [might contain unicode characters that can't
be converted to
Mark Dufour wrote:
You forgot to check for an error when:
o when you wrote f.error [attribute error might not exist e.g. f is
None]
o you called str(f.error) [might contain unicode characters that can't
be converted to a string using the
You have achieved so much with the first release of Shed Skin that it's
strange to see you apparently trying to argue that exceptions aren't
necessary when in fact they are such a fundamental part of Python's
philosophy.
To be honest, I am a relative newcomer to Python, and Shed Skin is the
Obviously, neither the 0 nor the message following should have been
displayed. It's a pity that this assumption was made, but given the short
time the project's been going I can understand it, hopefully Mark will
continue towards greater python compliance :)
The latter is certainly my goal. I
Mark Dufour wrote:
Obviously, neither the 0 nor the message following should have been
displayed. It's a pity that this assumption was made, but given the short
time the project's been going I can understand it, hopefully Mark will
continue towards greater python compliance :)
The latter is
Mark Dufour wrote:
The latter is certainly my goal. I just haven't looked into supporting
exceptions yet, because I personally never use them. I feel they
should only occur in very bad situations, or they become goto-like
constructs that intuitively feel very ugly. In the 5500 lines of the
On 9/12/05, Brian Quinlan [EMAIL PROTECTED] wrote:
Mark Dufour wrote:
The latter is certainly my goal. I just haven't looked into supporting
exceptions yet, because I personally never use them. I feel they
should only occur in very bad situations, or they become goto-like
constructs that
In general it's considered quite pythonic to catch exceptions :-)
It's a particularly useful way of implementing duck typing for example.
I'm not sure if I've got *any* code that doesn't use exceptions
somewhere
Hehe. Okay. It will probably always be the case that you have to lose
some Python
A.B., Khalid wrote:
Mark Dufour wrote:
After nine months of hard work, I am proud to introduce my baby to the
world: an experimental Python-to-C++ compiler.
Good work.
I have good news and bad news.
First the good news: ShedSkin (SS) more or less works on Windows. After
patching gc6.5
I am reluctant to attempt an arduous installation on Windows, but if
Mr. Dufour or someone else could create a web site that would let you
paste in Python code and see a C++ translation, I think this would
expand the user base. Alternatively, a Windows executable would be
nice.
The web site is a
Hi!
adDoc's networker Phil wrote:
experimental Python-to-C++ compiler.
why that instead of Pypy?
. pypy compiles to llvm (low-level virtual machine) bytecode
which is obviously not as fast as the native code coming from c++ compilers;
PyPy can currently compile Python code to
After nine months of hard work, I am proud to introduce my baby to the
world: an experimental Python-to-C++ compiler.
Wow, looks really cool. But why that instead of Pypy?
I agree with anyone that a JIT compiler that supports the full Python
semantics (which I thought to be the goal of PyPy?)
Carl Friedrich Bolz wrote:
. there is no reason why the pypy project can't have a .NET architecture
instead of the java-like arrangement I assume it has now
Sorry, I can't really follow you here. In what way does PyPy have a
Java-like arrangement?
I imagine that this remark was made in
Mark Dufour wrote:
With this initial release, I hope to attract other people to help me
locate remaining problems,
Well, you did say you want help with locating problems. One problem with
this is it doesn't build...
If I try and build (following your instructions), I get presented with a
Hi Paul!
Paul Boddie wrote:
Carl Friedrich Bolz wrote:
. there is no reason why the pypy project can't have a .NET architecture
instead of the java-like arrangement I assume it has now
Sorry, I can't really follow you here. In what way does PyPy have a
Java-like arrangement?
I imagine that
Michael Sparks wrote:
Well, you did say you want help with locating problems. One problem with
this is it doesn't build...
I found that I needed both the libgc and libgc-dev packages for my
Kubuntu distribution - installing them fixed the include issues that
you observed - and it does appear to
Mark Dufour wrote:
After nine months of hard work, I am proud to introduce my baby to the
world: an experimental Python-to-C++ compiler.
Good work.
I have good news and bad news.
First the good news: ShedSkin (SS) more or less works on Windows. After
patching gc6.5 for MinGW, building it, and
Hi Mark!
Mark Dufour wrote:
After nine months of hard work, I am proud to introduce my baby to the
world: an experimental Python-to-C++ compiler.
Wow, looks really cool. But why that instead of Pypy?
I agree with anyone that a JIT compiler that supports the full Python
semantics (which I
Paul Boddie wrote:
Michael Sparks wrote:
Well, you did say you want help with locating problems. One problem with
this is it doesn't build...
I found that I needed both the libgc and libgc-dev packages for my
Kubuntu distribution - installing them fixed the include issues that
you
Carl Friedrich Bolz wrote:
a) building LLVM is not _that_ bad (you don't need to build the
C-frontend, which is the really messy part)
That piece of wisdom must have passed me by last time, when I probably
heeded the scary warning from the configure script and made the mistake
of getting the C
Mark Dufour [EMAIL PROTECTED] writes:
After nine months of hard work, I am proud to introduce my baby to the
world: an experimental Python-to-C++ compiler.
Wow, looks really cool. But why that instead of Pypy?
--
http://mail.python.org/mailman/listinfo/python-list
experimental Python-to-C++ compiler.why that instead of Pypy?
. pypy compiles to llvm (low-level virtual machine) bytecode
which is obviously not as fast as the native code coming from c++ compilers;
but the primary mission of pypy
is just having a python system that is
written in something
After nine months of hard work, I am proud to introduce my baby to the
world: an experimental Python-to-C++ compiler. It can convert many
Python programs into optimized C++ code, without any user intervention
such as adding type declarations. It uses rather advanced static type
inference
28 matches
Mail list logo
