Python Distilled

[Simon Wittber]

I want to build a Python2.5 interpreter for an embedded system. I only
have 4MB of RAM to play with, so I want to really minimise the python
binary.

Things I can think of removing safely are:
- Unicode
- Long numbers
- Complex number
- Compiler / Parser
- Thread support
- OS specific stuff

I'd also like to remove any deprecated or stuff which is left in for
backwards functionality (eg Classic classes).

Google tells me that people have done this before, back in Python1.5.2
days. Has anyone tried to do this recently with a more modern Python?

-Sw.

[Marc 'BlackJack' Rintsch]

In <11**********************@m73g2000cwd.googlegroups .com>, Simon Wittber
wrote:

I'd also like to remove any deprecated or stuff which is left in for
backwards functionality (eg Classic classes).

Classic classes are still needed for exceptions:

>>class E(object):

.... pass
....

>>raise E

Traceback (most recent call last):
File "<stdin>", line 1, in <module>
TypeError: exceptions must be classes, instances, or strings (deprecated),
not type

Ciao,
Marc 'BlackJack' Rintsch

[Georg Brandl]

Marc 'BlackJack' Rintsch wrote:

In <11**********************@m73g2000cwd.googlegroups .com>, Simon Wittber
wrote:

>I'd also like to remove any deprecated or stuff which is left in for
backwards functionality (eg Classic classes).

Classic classes are still needed for exceptions:

>>>class E(object):

... pass
...

>>>raise E

Traceback (most recent call last):
File "<stdin>", line 1, in <module>
TypeError: exceptions must be classes, instances, or strings (deprecated),
not type

The error is a bit misleading, since in Python 2.5 all exceptions are new-style,
but new exception classes must be derived from an existing one.
Classic classes, their instances and strings are only allowed for backwards
compatibility.

Georg

[Jorge Godoy]

Marc 'BlackJack' Rintsch <bj****@gmx.netwrites:

In <11**********************@m73g2000cwd.googlegroups .com>, Simon Wittber
wrote:

>I'd also like to remove any deprecated or stuff which is left in for
backwards functionality (eg Classic classes).

Classic classes are still needed for exceptions:

>>>class E(object):

... pass
...

>>>raise E

Traceback (most recent call last):
File "<stdin>", line 1, in <module>
TypeError: exceptions must be classes, instances, or strings (deprecated),
not type

On the other hand...

>>import exceptions
class E(exceptions.Exception):

.... pass
....

>>raise E

Traceback (most recent call last):
File "<stdin>", line 1, in ?
__main__.E

>>>

This also has the advantage to let it explicit in the code that E is an
exception.
--
Jorge Godoy <jg****@gmail.com>

[Paul McGuire]

"Marc 'BlackJack' Rintsch" <bj****@gmx.netwrote in message
news:pa****************************@gmx.net...

In <11**********************@m73g2000cwd.googlegroups .com>, Simon Wittber
wrote:

>I'd also like to remove any deprecated or stuff which is left in for
backwards functionality (eg Classic classes).

Classic classes are still needed for exceptions:

>>>class E(object):

... pass
...

>>>raise E

Traceback (most recent call last):
File "<stdin>", line 1, in <module>
TypeError: exceptions must be classes, instances, or strings (deprecated),
not type

Ciao,
Marc 'BlackJack' Rintsch

I thought exceptions were converted to new-style classes for Py2.5
(http://docs.python.org/whatsnew/pep-352.html). I've not upgraded yet, so
cannot easily test this - under what version of Python was your posted code
run?

-- Paul

[Georg Brandl]

Paul McGuire wrote:

"Marc 'BlackJack' Rintsch" <bj****@gmx.netwrote in message
news:pa****************************@gmx.net...

>In <11**********************@m73g2000cwd.googlegroups .com>, Simon Wittber
wrote:

>>I'd also like to remove any deprecated or stuff which is left in for
backwards functionality (eg Classic classes).

Classic classes are still needed for exceptions:

>>>>class E(object):

... pass
...

>>>>raise E

Traceback (most recent call last):
File "<stdin>", line 1, in <module>
TypeError: exceptions must be classes, instances, or strings (deprecated),
not type

Ciao,
Marc 'BlackJack' Rintsch

I thought exceptions were converted to new-style classes for Py2.5
(http://docs.python.org/whatsnew/pep-352.html).

Yes, they were. Still, you can't raise instance of arbitrary new-style classes
as exceptions, and you will never be able to. In Py3k, only instances of
"BaseException" subclasses will be raisable.

Georg

[Steven Bethard]

Simon Wittber wrote:

I want to build a Python2.5 interpreter for an embedded system. I only
have 4MB of RAM to play with, so I want to really minimise the python
binary.

[snip]

Google tells me that people have done this before, back in Python1.5.2
days. Has anyone tried to do this recently with a more modern Python?

http://www.python.org/dev/summary/20...rinking-python

STeVe

[Simon Wittber]

http://www.python.org/dev/summary/20...rinking-python

Excellent, just what I was hoping for. Thanks!

-Sw.

[The Eternal Squire]

Try also Diet Python on SourceForge.

It's the first step toward a shrunken Python for embedded Win32
systems.

Cheers,

The Eternal Squire
Simon Wittber wrote:

http://www.python.org/dev/summary/20...rinking-python

Excellent, just what I was hoping for. Thanks!

-Sw.