Many thanks to everyone,
I have now different options to try out and present to my users.
Dave Kuhlman wrote:
> Alan Kennedy <jython-users <at> xhaus.com> writes:
>>> So if I have to ask my users to re-write their scripts (when the problem
>>> is encountered), what would be the easier way to split the script in
>>> different compilation units without having to change much of the logic
>>> and sharing the main name space ?
>> You could just simply present a counter of how many statements have
>> been executed so far in the session, e.g. for statement 54 in a
>> session, the prompt would look like this
> [good suggestions by Alan Kennedy snipped]
> And, don't forget about the cmd module in the standard library:
> With very little work you could implement your own interactive interface to the
> Jython interpreter. Using the cmd module, it is easy to implement special
> commands (for example the checkpoint feature that Alan suggested), or to
> maintain a history of jython statements entered by the user and write them to a
> file when the user "check-points", etc.
> By the way, has any work been done to port IPython to Jython? I read a message
> on the IPython email list that indicated that the IPython project attempts to
> keep IPython in all Python (not C) code. So, it sounds reasonably do-able.
> When I tryied just now to run IPython with Jython 2.2.1, it told me that only
> versions of Python 2.3 and later are supported. So, maybe we have to wait for
> the next version of Jython.
> One more point -- When I run the jython interactive interpreter on Linux, I use
> $ rlwrap -r jython
> The -r/--remember flag tells rlwrap to save a history file for me. I don't
> know about the availability of rlwrap on MS Windows, though.
> - Dave
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> Jython-users mailing list
This message and any attachments are intended for the use of the addressee or addressees only. The
unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its content
is prohibited. If you received this message in error, please delete it from your system and notify
the sender. E-mails can be altered and their integrity cannot be guaranteed. ESA shall not be liable
for any e-mail if modified.