Re: Python 1.2 beta 3 compiling problems + many other questions

Guido.van.Rossum@cwi.nl
Sun, 09 Apr 1995 23:37:46 +0200

> I've compiled Python v1.2 beta 3 on an Intel machine under the UNIX
> platform called QNX and everything works great. However, when I
> change the options in the general Makefile to choose compiling using
> 16 bit instead of 32 and a Large memory model instead of the default
> which is small, the executable which is made fails its tests (make
> test).

Try to be more precise. Run this command:

PYTHONPATH=../Lib:../Lib/test:./Modules ./python -c 'import testall'

and let me know what the last few lines of output are before it stops.

It *should* work with 16 bits -- I've built a 16 bit version for the
mac and used it for years before the Mac compiler I was using had a
decent 32-bit mode...

> Another question I have is that I'd like to use the '@' character.
> I've read the python doc's and it blatently states not to, but our
> software uses variable of the sort :
>
> object.attribute.value
>
> where value can be @float, @integer, @string, @time, @date, etc.
>
> Am I going to be able to get our variables into Python without a
> nomenclature change?

I'm not sure whether you use the '@float' etc. as a type indicator,
but I presume that a tiny change in the lexical analyzer
(Parser/tokenizer.c) would make it possible to use '@' as an
alphabetic character in identifiers. You can't call it Python then,
but you could call it '@ython' I presume :-)

> Also, these variable in our software are being held in a constantly
> updating database. Will I be able to setup Python functions to
> execute based on passed exceptions or will I need to create an event
> loop which will poll for changes? I haven't noticed any timers
> (although I haven't looked too hard) in Python. What's the story
> here, since I'd also like to do some timed events?

Python itself is not event based at all, but if you plan to embed
Python in your system I presume that you can have your own event loop
and call the Python interpreter when it is needed. You can also use
UNIX signals to execute signal handlers written in Python at specific
times.

--Guido van Rossum, CWI, Amsterdam <mailto:guido@cwi.nl>
<http://www.cwi.nl/~guido/>