Skip to main content

Announce: ExtSession

As a support package for some other things, I've written a little module called ExtSession. The basic idea is to have an easy way to control a python session running in another process. You can simply instansiate the ExtSession class, and call the execute() method. The results are asyncronous-like, but will be improved later. Very likely support will be added to get Deferreds. For now, you can simply poll or wait. The results of each execute() call (best done one line at a time) are seperated and returned individually of output from other commands, making it very easy to work with over a session's lifetime.

Following is a stripped pydoc pull of the docstrings. I hope someone finds this as useful as I think I will.

NAME
extsession

FILE
/home/calvin/extsession/extsession.py

DESCRIPTION
ExtSession Module
For executing code in an external interpreter.

There are many cases where operations are either intensive or blocking by
waiting, and in both situations the extsession module can be used to control
a python session in a seperate process for the purposes of executing code
in parellel without the dangers associated with threads or the complexities
in dealing with asyncronous frameworks.

The core of extsession is the ExtSession class. See its help for details.

Also, look at the exteval and extexec functions for quick, blocking code
execution in a fresh interpreter. (note: these functions do not execute in
parellel, only in a seperate process, but blocking the original)

CLASSES
__builtin__.object
ExtEval
ExtResults
ExtSession
Session

class ExtEval(__builtin__.object)
| Evaluates expressions in a new process with an asyncronous result.
|
| The result attribute evaluates to the result of the expression, or access
| raises a ValueError, if the result is not ready.
|
| Methods defined here:
|
| __init__(self, expr)
|
| ----------------------------------------------------------------------
| Properties defined here:
|
| result
| = _get_result(self)
| Get the result only if its ready.
|
| ----------------------------------------------------------------------
| Data and other attributes defined here:
|
| __dict__ =
| dictionary for instance variables (if defined)
|
| __weakref__ =
| list of weak references to the object (if defined)

class ExtResults(__builtin__.object)
| Represents results from an operation in another process.
|
| Methods defined here:
|
| __init__(self, stdout, stderr, done)
|
| read(self, size=None)
| Read data from stdout of process from operation.
| Raises ValueError if the operation is not complete.
|
| wait(self)
| Return only when the operation is complete.
|
| ----------------------------------------------------------------------
| Data and other attributes defined here:
|
| __dict__ =
| dictionary for instance variables (if defined)
|
| __weakref__ =
| list of weak references to the object (if defined)

class ExtSession(__builtin__.object)
| Controls a python session in another process.
|
| Methods defined here:
|
| __getitem__(self, name)
|
| __init__(self)
|
| execute(self, source)
| Execute arbitrary python source.
| Returns an ExtResults object to access the results.
|
| exit(self, code=0)
|
| readcodes(self)
|
| readline(self)
|
| writeline(self, line)
|
| ----------------------------------------------------------------------
| Data and other attributes defined here:
|
| __dict__ =
| dictionary for instance variables (if defined)
|
| __weakref__ =
| list of weak references to the object (if defined)

class Session(__builtin__.object)
| Manages the session in this process. Used by ExtSession in spawned
| interpreters. Can also be used for a very light sandbox in the same
| process.
|
| Methods defined here:
|
| __init__(self)
|
| execute(self, source, stdout_fn=None, stderr_fn=None, done_fn=None)
| Executes code in a semi-controlled environment and redirects output
| to given stdout and stderr filenames, or random temp locations. Writes
| a code to the file at done_fn when finished. A code of 'DONE' is
| expected. When a code appears in the done file, the stdout and stderr
| files are ready for reading and are complete.
|
| ----------------------------------------------------------------------
| Data and other attributes defined here:
|
| __dict__ =
| dictionary for instance variables (if defined)
|
| __weakref__ =
| list of weak references to the object (if defined)

FUNCTIONS
exteval(expression)
Creates a new process running a new python interpreter, evaluates the
given expression, and returns the result. The result must be basic types,
but may expand in the future to any pickle-capable type.

extexec(source)
Creates a new process, executes the source in a new python interpreter,
and returns a tuple of the stdout and stderr captured.

sleep(...)
sleep(seconds)

Delay execution for a given number of seconds. The argument may be
a floating point number for subsecond precision.

Comments

Anonymous said…
It looks interesting. But can you provide an example? Even if it's only executing Hello World and reading in the results again from the main process.

Popular posts from this blog

CARDIAC: The Cardboard Computer

I am just so excited about this. CARDIAC. The Cardboard Computer. How cool is that? This piece of history is amazing and better than that: it is extremely accessible. This fantastic design was built in 1969 by David Hagelbarger at Bell Labs to explain what computers were to those who would otherwise have no exposure to them. Miraculously, the CARDIAC (CARDboard Interactive Aid to Computation) was able to actually function as a slow and rudimentary computer.  One of the most fascinating aspects of this gem is that at the time of its publication the scope it was able to demonstrate was actually useful in explaining what a computer was. Could you imagine trying to explain computers today with anything close to the CARDIAC? It had 100 memory locations and only ten instructions. The memory held signed 3-digit numbers (-999 through 999) and instructions could be encoded such that the first digit was the instruction and the second two digits were the address of memory to operate on

Statement Functions

At a small suggestion in #python, I wrote up a simple module that allows the use of many python statements in places requiring statements. This post serves as the announcement and documentation. You can find the release here . The pattern is the statement's keyword appended with a single underscore, so the first, of course, is print_. The example writes 'some+text' to an IOString for a URL query string. This mostly follows what it seems the print function will be in py3k. print_("some", "text", outfile=query_iostring, sep="+", end="") An obvious second choice was to wrap if statements. They take a condition value, and expect a truth value or callback an an optional else value or callback. Values and callbacks are named if_true, cb_true, if_false, and cb_false. if_(raw_input("Continue?")=="Y", cb_true=play_game, cb_false=quit) Of course, often your else might be an error case, so raising an exception could be useful

How To Teach Software Development

How To Teach Software Development Introduction Developers Quality Control Motivation Execution Businesses Students Schools Education is broken. Education about software development is even more broken. It is a sad observation of the industry from my eyes. I come to see good developers from what should be great educations as survivors, more than anything. Do they get a headstart from their education or do they overcome it? This is the first part in a series on software education. I want to open a discussion here. Please comment if you have thoughts. Blog about it, yourself. Write about how you disagree with me. Write more if you don't. We have a troubled industry. We care enough to do something about it. We hark on the bad developers the way people used to point at freak shows, but we only hurt ourselves but not improving the situation. We have to deal with their bad code. We are the twenty percent and we can't talk to the eighty percent, by definition, so we need to impro