Thank you for the hint: it works. :)
Cesare
In data 21 agosto 2008 alle ore 17:34:56, Curt Hagenlocher <[EMAIL PROTECTED]>
ha scritto:
> On Thu, Aug 21, 2008 at 7:09 AM, Cesare Di Mauro
> <[EMAIL PROTECTED]> wrote:
>>
>>>>> import Tkinter
>> Traceba
On 27 agu 2008 at 08:46:15, Kilian Klimek <[EMAIL PROTECTED]> wrote:
> Hello,
>
> i know this has been discusses very much, i'm sorry,
> but i can't help it. In a nutshell, the proposal is as
> follows:
>
> 1. Self remains explicit (like it is now).
> 2. if a class is a subclass of a special class
On 03 sep 2008 at 00:50:13, M.-A. Lemburg <[EMAIL PROTECTED]> wrote:
> There already is a menu entry that starts the Python interpreter
> on Windows, so why not use that ?
Because i need to start Python from folders which have
files that define a specific "environment".
I have several servers an
On 03 Sep 2008 at 13:34:18, M.-A. Lemburg <[EMAIL PROTECTED]> wrote:
> Same here, but I usually have a env.bat that sets up whatever
> environment I need (including the required Python version) and
> run that when opening a prompt to work on a particular project.
> IMHO, the only point of having
Have you made some benchmarks like pystone?
Cheers,
Cesare
On Wed, Jan 21, 2009 08:50PM, Luke Kenneth Casson Leighton wrote:
> this is a progress report on compiling python using entirely free
> software tools, no proprietary compilers or operating systems
> involved, yet still linking and succes
Looking at the UNARY_NOT case in ceval.c:
case UNARY_NOT:
v = TOP();
err = PyObject_IsTrue(v);
Py_DECREF(v);
if (err == 0) {
Py_INCREF(Py_True);
2011/8/30 Antoine Pitrou
> Changing the bytecode width wouldn't make the interpreter more complex.
It depends on the kind of changes. :)
WPython introduced a very different "intermediate code" representation that
required a big change on the peepholer optimizer on 1.0 alpha version.
On 1.1 fi
2011/8/30 Nick Coghlan
>
> Yeah, it's definitely a trade-off - the point I was trying to make is
> that there *is* a trade-off being made between complexity and speed.
>
> I think the computed-gotos stuff struck a nice balance - the macro-fu
> involved means that you can still understand what the
2011/8/30 stefan brunthaler
> Yes, indeed I have a more straightforward instruction format to allow
> for more efficient decoding. Just going from bytecode size to
> word-code size without changing the instruction format is going to
> require 8 (or word-size) times more memory on a 64bit system.
2011/8/30 stefan brunthaler
> > Do I sense that the bytecode format is no longer platform-independent?
> > That will need a bit of discussion. I bet there are some things around
> > that depend on that.
> >
> Hm, I haven't really thought about that in detail and for longer, I
> ran it on PowerPC
2011/8/31 Terry Reedy
> I find myself more comfortable with the Cesare Di Mauro's idea of expanding
> to 16 bits as the code unit. His basic idea was using 2, 4, or 6 bytes
> instead of 1, 3, or 6.
>
It can be expanded to longer than 6 bytes opcodes, if needed. The format is
designed to be flexi
2011/8/31 stefan brunthaler
> > I think that you must deal with big endianess because some RISC can't
> handle
> > at all data in little endian format.
> >
> > In WPython I have wrote some macros which handle both endianess, but
> lacking
> > big endian machines I never had the opportunity to ver
2011/8/31 Guido van Rossum
> On Tue, Aug 30, 2011 at 10:04 PM, Cesare Di Mauro
> wrote:
> > It isn't, because motivation to do something new with CPython vanishes,
> at
> > least on some areas (virtual machine / ceval.c), even having some ideas
> to
> > exp
2011/9/1 Ned Batchelder
> When the switchover to the new instruction format happens, what happens to
> sys.settrace() tracing? Will it report the same sequence of line numbers?
> For a small but important class of program executions, this is more
> important than speed.
>
> --Ned
>
A simple s
2011/9/1 Mark Shannon
> Cesare Di Mauro wrote:
>
>> 2011/9/1 Ned Batchelder > n...@nedbatchelder.com>>
>>
>>
>>When the switchover to the new instruction format happens, what
>>happens to sys.settrace() tracing? Will it report the same seq
2012/7/18 Victor Stinner
> I don't expect to run a program 10x faster, but I would be happy if I
> can run arbitrary Python code 25% faster.
>
If that's your target, you don't need to resort to a
bytecode-to-binary-equivalent compiler. WPython already gave similar
results with Python 2.6.
The i
2012/7/18 Steven D'Aprano
> WPython in particular seems to be very promising, and quite fast. I don't
> understand why it doesn't get more attention (although I admit I can't
> criticise, since I haven't installed or used it myself).
>
>
> http://www.pycon.it/media/stuff/slides/beyond-bytecode-a-
101 - 117 of 117 matches
Mail list logo
