Hi all,
I've just released Shed Skin 0.0.25. Together with the (unannounced)
0.0.24 release, there have been some interesting changes. Most
importantly perhaps, Shed Skin now caches (most) 1-length strings,
which can improve performance dramatically for string-intensive
programs. I also performed
On Aug 22, 10:00 am, srepmub <[EMAIL PROTECTED]> wrote:
> > Adding socket support would certainly open the door for many common
> > classes applications. If I had my pick, I say, sockets and then re.
>
> Thanks. Especially sockets should be not too hard to add, but I
> probably won't work on these
> Adding socket support would certainly open the door for many common
> classes applications. If I had my pick, I say, sockets and then re.
Thanks. Especially sockets should be not too hard to add, but I
probably won't work on these directly myself. Let me know if you are
interested.. :-)
> BTW
On Aug 20, 7:31 am, "Mark Dufour" <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> I have just released Shed Skin 0.0.23. It doesn't contain the type
> inference scalability improvements I was working on, but it does have
> quite a few bug fixes and minor feature additions. Here's a list of
> changes:
>
>
On Aug 20, 7:31 am, "Mark Dufour" <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> I have just released Shed Skin 0.0.23. It doesn't contain the type
> inference scalability improvements I was working on, but it does have
> quite a few bug fixes and minor feature additions. Here's a list of
> changes:
>
>
Hi all,
I have just released Shed Skin 0.0.23. It doesn't contain the type
inference scalability improvements I was working on, but it does have
quite a few bug fixes and minor feature additions. Here's a list of
changes:
-support for __iadd__, __imul__ and such (except __ipow__ and __imod__)
-so
hi mike,
> Great work. You might want to advertise this on the main site
> (currently it states that this is impossible).
yes, thank you for reminding me.
> You've said somewhere that you didn't/don't plan on working on this
> aspect, but it is surely the "killer feature" of shed skin needed to
On Jun 29, 3:48 am, "Mark Dufour" <[EMAIL PROTECTED]> wrote:
> I have just released version 0.0.22 of Shed Skin, an experimental
> Python-to-C++ compiler. Among other things, it has the exciting new
> feature of being able to generate (simple, for now) extension modules,
> so it's much easier to c
hi felix,
On 6/29/07, felix seltzer <[EMAIL PROTECTED]> wrote:
> does this project include support for pygtk type GUI's?
No, it won't work for arbitrary python programs. Shed Skin is
currently limited to smallish programs (up to a few hundred lines),
that only use a few basic modules (random, mat
On Jun 29, 7:48 am, "Mark Dufour" <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> I have just released version 0.0.22 of Shed Skin, an experimental
> Python-to-C++ compiler. Among other things, it has the exciting new
> feature of being able to generate (simple, for now) extension modules,
> so it's much
does this project include support for pygtk type GUI's?
On 6/29/07, Mark Dufour <[EMAIL PROTECTED]> wrote:
Hi all,
I have just released version 0.0.22 of Shed Skin, an experimental
Python-to-C++ compiler. Among other things, it has the exciting new
feature of being able to generate (simple, fo
Hi all,
I have just released version 0.0.22 of Shed Skin, an experimental
Python-to-C++ compiler. Among other things, it has the exciting new
feature of being able to generate (simple, for now) extension modules,
so it's much easier to compile parts of a program and use them (by
just importing the
On 2 Apr, 20:17, "Kay Schluehr" <[EMAIL PROTECTED]> wrote:
>
> Note that the conflict of putting modules on top level or better
> within separate packages is not an either-or decision from a
> programmers point of view who just wants to access those modules. A
> top level module like lib or std can
On Apr 2, 1:27 pm, "Paul Boddie" <[EMAIL PROTECTED]> wrote:
> On 2 Apr, 13:05, [EMAIL PROTECTED] wrote:
>
>
>
> > There is some possibility that Python 3.1 will have what you ask
> > for:http://www.python.org/dev/peps/pep-3108/
>
> Prior to that PEP being written/published, I made this proposal:
>
Paul Boddie:
> Prior to that PEP being written/published, I made this proposal:
> http://wiki.python.org/moin/CodingProjectIdeas/StandardLibrary/Restru...
On first sight it looks good. Python 3.0-3.1 is the best and probably
only possibility for such improvement (I have said 3.1 too because I
thin
On 2 Apr, 13:05, [EMAIL PROTECTED] wrote:
>
> There is some possibility that Python 3.1 will have what you ask
> for:http://www.python.org/dev/peps/pep-3108/
Prior to that PEP being written/published, I made this proposal:
http://wiki.python.org/moin/CodingProjectIdeas/StandardLibrary/Restructur
Paul Boddie:
> the author's frustration with the state of the standard library:
> something which almost always gets mentioned in people's pet Python
> hates, but something mostly ignored in the wider enthusiasm for
> tidying up the language.
There is some possibility that Python 3.1 will have wha
On Apr 2, 9:17 am, John Nagle <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] wrote:
> > but in any case, I believe there are several reasons why type
> > inference scalability is actually not _that_ important (as long as it
> > works and doesn't take infinite time):
>
> > -I don't think we want to
On 2 Apr, 09:17, John Nagle <[EMAIL PROTECTED]> wrote:
>
> Something else worth trying: type inference for separately
> compiled modules using the test cases for the modules.
I mentioned such possibilities once upon a time:
http://blog.amber.org/2004/12/23/static-typing-and-python/
Note the
[EMAIL PROTECTED] wrote:
> but in any case, I believe there are several reasons why type
> inference scalability is actually not _that_ important (as long as it
> works and doesn't take infinite time):
>
> -I don't think we want to do type inference on large Python programs.
> this is indeed askin
> You still dream of this, isn't it? Type inference in dynamic languages
> doesn't scale. It didn't scale in twenty years of research on
> SmallTalk and it doesn't in Python. However there is no no-go theorem
type inference sure is difficult business, and I won't deny there are
scalability issues
Kay Schluehr wrote:
> On Apr 1, 6:07 pm, John Nagle <[EMAIL PROTECTED]> wrote:
>
>>Kay Schluehr wrote:
>>
>>>Indeed. The only serious problem from an acceptance point of view is
>>>that Mark tried to solve the more difficult problem first and hung on
>>>it. Instead of integrating a translator/comp
On Apr 1, 6:07 pm, John Nagle <[EMAIL PROTECTED]> wrote:
> Kay Schluehr wrote:
> > Indeed. The only serious problem from an acceptance point of view is
> > that Mark tried to solve the more difficult problem first and hung on
> > it. Instead of integrating a translator/compiler early with CPython,
[EMAIL PROTECTED] writes:
> > I don't see how that can be--we're talking about a GCC-based compiler,
> > right?
>
> no, Shed Skin is a completely separate entity,
I was referring to GNAT.
--
http://mail.python.org/mailman/listinfo/python-list
> I don't see how that can be--we're talking about a GCC-based compiler,
> right?
no, Shed Skin is a completely separate entity, that outputs C++ code.
it's true I only use GCC to test the output, and I use some GCC-
specific extensions (__gnu_cxx::hash_map/hash_set), but people have
managed to c
Kay Schluehr wrote:
> Indeed. The only serious problem from an acceptance point of view is
> that Mark tried to solve the more difficult problem first and hung on
> it. Instead of integrating a translator/compiler early with CPython,
> doing some factorization of Python module code into compilable
> Anyway, the only real point is that if there is a concern about the
> copyright and licensing of the output of ShedSkin, then we merely need
> to ask the author of it to clarify matters and move on with life. With
> the exception of GNAT, to date no GPL'd compiler has ever placed a GPL
> restric
On Mar 31, 11:26 pm, "Luis M. González" <[EMAIL PROTECTED]> wrote:
> On Mar 31, 8:38 am, Bjoern Schliessmann
>
>
> [EMAIL PROTECTED]> wrote:
> > Mark Dufour wrote:
> > > Shed Skin allows for translation of pure (unmodified), implicitly
> > > statically typed Python programs into optimized C++, and
Mark Dufour wrote:
> Hi all,
>
> I have recently released version 0.0.20 and 0.0.21 of Shed Skin, an
> optimizing Python-to-C++ compiler. Shed Skin allows for translation of
> pure (unmodified), implicitly statically typed Python programs into
> optimized C++, and hence, highly optimized machine l
On Sat, 2007-03-31 at 20:47 -0700, Paul Rubin wrote:
> Michael Torrie <[EMAIL PROTECTED]> writes:
> > The no-service contract version of the GPL is not the same as the
> > standard GPLv2.
>
> I don't see how that can be--we're talking about a GCC-based compiler,
> right?
I found the real reason w
On Sat, 2007-03-31 at 20:47 -0700, Paul Rubin wrote:
> Michael Torrie <[EMAIL PROTECTED]> writes:
> > The no-service contract version of the GPL is not the same as the
> > standard GPLv2.
>
> I don't see how that can be--we're talking about a GCC-based compiler,
> right?
Well, that's beside the p
Michael Torrie <[EMAIL PROTECTED]> writes:
> The no-service contract version of the GPL is not the same as the
> standard GPLv2.
I don't see how that can be--we're talking about a GCC-based compiler,
right?
--
http://mail.python.org/mailman/listinfo/python-list
On Sun, 2007-04-01 at 02:49 +, Dennis Lee Bieber wrote:
> Take that up with ACT... GNAT 3.15p was explicitly unencumbered, but
> the current version of GNAT, in the GPL (no-service contract) form has
> gone the other direction, claiming that executables must be released
> GPL.
The no-ser
On Mar 31, 10:31 pm, Bjoern Schliessmann wrote:
> Luis M. González wrote:
> > I think he should be taken very seriously.
>
> Agreed.
>
> Okay, it seems focusing a discussion on one single point is
> difficult for many people. Next time I'll be mind-bogglingly clear
> that even the last one underst
Luis M. González wrote:
> I think he should be taken very seriously.
Agreed.
Okay, it seems focusing a discussion on one single point is
difficult for many people. Next time I'll be mind-bogglingly clear
that even the last one understands after reading it one time ...
Regards,
Björn
Fup2 p
"Paul McGuire" <[EMAIL PROTECTED]> writes:
> Why would that be? GPL'ed code libraries can be a turn-off for those
> who want to release commercial products using them, but a GPL'ed
> utility such as a compiler bears no relationship or encumbrance on the
> compiled object code it generates.
For so
On Mar 31, 6:45 pm, Alexander Schmolck <[EMAIL PROTECTED]> wrote:
> Regardless of its merrits, it's GPL'ed which I assume is an immediate turn-off
> for many in the community.
>
Why would that be? GPL'ed code libraries can be a turn-off for those
who want to release commercial products using them
Alexander Schmolck wrote:
>
> Regardless of its merrits, it's GPL'ed which I assume is an immediate turn-off
> for many in the community.
In the way that tools such as gcc are GPL-licensed, or do you have
something else in mind?
Paul
--
http://mail.python.org/mailman/listinfo/python-list
"Luis M. González" <[EMAIL PROTECTED]> writes:
> On Mar 31, 8:38 am, Bjoern Schliessmann [EMAIL PROTECTED]> wrote:
> > Mark Dufour wrote:
> > > Shed Skin allows for translation of pure (unmodified), implicitly
> > > statically typed Python programs into optimized C++, and hence,
> >
> >
On Mar 31, 8:38 am, Bjoern Schliessmann wrote:
> Mark Dufour wrote:
> > Shed Skin allows for translation of pure (unmodified), implicitly
> > statically typed Python programs into optimized C++, and hence,
>
>^> highly
> optimized ma
[EMAIL PROTECTED] wrote:
> Why are you taking potshots at Mark?
What suggests that I'm "taking potshots" at Mark?
> He's maybe onto something and he's asking for help. If he can
> generate efficient C++ code from implicitly statically type Python
> it stands to reason that he can take advantag
Björn> Mark Dufour wrote:
>> Shed Skin allows for translation of pure (unmodified), implicitly
>> statically typed Python programs into optimized C++, and hence,
>> highly optimized machine language.
Bjoern>
Bjoern> Wow, I bet all C++ compiler manufactur
Mark Dufour wrote:
> Shed Skin allows for translation of pure (unmodified), implicitly
> statically typed Python programs into optimized C++, and hence,
^
> highly optimized machine language.
Wow, I bet all C++ com
Hi all,
I have recently released version 0.0.20 and 0.0.21 of Shed Skin, an
optimizing Python-to-C++ compiler. Shed Skin allows for translation of
pure (unmodified), implicitly statically typed Python programs into
optimized C++, and hence, highly optimized machine language. Besides
many bug fixes
Hi all,
I have just released version 0.0.19 of Shed Skin, an optimizing
Python-to-C++ compiler. It allows for translation of pure
(unmodified), implicitly statically typed Python programs into
optimized C++, and hence, highly optimized machine language. This
latest release adds basic support for i
hi all,
I have just released Shed Skin 0.0.18. besides many fixes and
optimizations, this release should work on OSX and 64-bit systems
(thanks john, larry, gustavo and denis!)
more interestingly, I collected 25 'largish' programs (at a total of
more than 6,000 lines!) that work fine with Shed Sk
Hello all,
As Bearophile pointed out, I have just released Shed Skin 0.0.8. For
those of you that do not know Shed Skin, it is an optimizing
Python-to-C++ compiler, that allows for translation of pure
(unmodified) Python programs into optimized machine language. The
speed of generated code is typi
I've been following this project with great interest. If you don't
mind me asking, can you please include links, if available, when you
post updates?
Great Stuff! Keep in coming!
Greg
--
http://mail.python.org/mailman/listinfo/python-list
Hello Python lovers,
I have just released Shed Skin 0.0.5.9. It's almost where I want it to be
for 0.0.6. What remains to be coded is some kind of connection to the
standard library (probably a simple one at first: working only for
'opaque handlers'). I also want to improve cases where ints and fl
Hi all,
I have just released Shed Skin 0.0.5. It fixes many bugs and adds many
minor features to the Python builtins, most notably, the 'set' class.
There have also been some optimizations on the C++ side. Finally, the
README now better explains the compiler's limitations, and a TODO file
has been
I'va got a trojan message by my virus scanner trying to download the
0.03 exe-file. Something to worry about?
Carl
Mark Dufour schrieb:
> Hi all,
>
> Thanks to the people trying out Shed Skin 0.0.2 and letting me know
> about several problems they encountered. I have released an updated
> versio
Hi all,
Thanks to the people trying out Shed Skin 0.0.2 and letting me know
about several problems they encountered. I have released an updated
version, 0.0.3. It contains some fixes, adds support for several
builtin functions (sorted, xrange..) and the Windows version is now a
mere 3 MB, instead
52 matches
Mail list logo
