Re: [Python-Dev] wpython is back

2009/11/27 Guido van Rossum > It's a Python implementation that uses wordcode instead of bytecode. > > http://code.google.com/p/wpython/ > > I don't see any benchmarks though. > You'll find some at page 28 here

Re: [Python-Dev] wpython is back

On Thu, Nov 26, 2009 at 3:41 PM, Georg Brandl wrote: > Cesare Di Mauro schrieb: >> Hi Mart >> >> I'm back with some news about wpython. I completed all the work that I >> was committed to do till the end of the year. I made a lot of changes to >> the code, that I'll report here.. > > For those of

Re: [Python-Dev] wpython is back

Cesare Di Mauro schrieb: > Hi Mart > > I'm back with some news about wpython. I completed all the work that I > was committed to do till the end of the year. I made a lot of changes to > the code, that I'll report here.. For those of us without an elephant's memory, could you please also recap wh

Re: [Python-Dev] Building a Windows MSI for Python /trunk

"Martin v. Löwis" writes: > It was too difficult to get right, plus nobody was interested in > using the daily MSI files. > > At some point, it was broken for several months (IIRC), with nobody > reporting that breakage. So when we noticed, we just turned the service > off. Sounds right - the da

[Python-Dev] wpython is back

Hi Mart I'm back with some news about wpython. I completed all the work that I was committed to do till the end of the year. I made a lot of changes to the code, that I'll report here. First, I added several conditional compilation sections that enable or disable almost every optimization I intro

Re: [Python-Dev] Building a Windows MSI for Python /trunk

>> You'll need to build release versions of Tcl/Tk/Tix. > > Yes, I saw a reference to that online, but I wasn't sure if that was the > problem -- is the naming convention really that 'tcl85g.lib' is the debug > lib!? Yes; Tcl apparently follows Unix conventions here rather than Windows convention

Re: [Python-Dev] Building a Windows MSI for Python /trunk

On Thu, Nov 26, 2009 at 09:54:35AM +0100, "Martin v. L?wis" wrote: > > First, the script that finds & builds the external dependencies has two > > minor problems. > > > > * it puts Tcl in tcl-8.*, and Tk in tk-8.*, but msi.py looks for them in > >tcl8.* and tk8.* to grab the license text. I

Re: [Python-Dev] PEP 391 ready for review

Nick Coghlan wrote: > Terry Reedy wrote: >> if not hasattr(factory, '__call__'): factory = __import__(factory) > > That won't quite work since the string generally isn't referring to a > module, and due to the quirk of __import__ returning the top level > module since that is what the interpreter

Re: [Python-Dev] PEP 391 ready for review

Terry Reedy wrote: > if not hasattr(factory, '__call__'): factory = __import__(factory) That won't quite work since the string generally isn't referring to a module, and due to the quirk of __import__ returning the top level module since that is what the interpreter needs to bind to a name as part

Re: [Python-Dev] Building a Windows MSI for Python /trunk

> First, the script that finds & builds the external dependencies has two > minor problems. > > * it puts Tcl in tcl-8.*, and Tk in tk-8.*, but msi.py looks for them in >tcl8.* and tk8.* to grab the license text. I changed the glob strings >appropriately and that seemed to work. Not sur

Re: [Python-Dev] PEP 391 ready for review

Dj Gilcrease gmail.com> writes: > > I would recommend removing the class keyword and replacing it with the > () as you have in the custom examples or replacing () with class so it > is uniform across all config options [snip] > > This just strikes me as odd to have to remember for built in hand

Re: [Python-Dev] PEP 391 ready for review

Terry Reedy udel.edu> writes: > [snip] Terry, Thanks for your helpful comments. I have checked in some changes to the PEP (r76533) which take into account the comments you made. Regards, Vinay Sajip ___ Python-Dev mailing list Python-Dev@python.or