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

Why I Switched From Git to Microsoft OneDrive

I made the unexpected move with a string of recent projects to drop Git to sync between my different computers in favor of OneDrive, the file sync offering from Microsoft. Its like Dropbox, but "enterprise."

Feeling a little ashamed at what I previously would have scoffed at should I hear of it from another developer, I felt a little write up of the why and the experience could be a good idea. Now, I should emphasize that I'm not dropping Git for all my projects, just specific kinds of projects. I've been making this change in habit for projects that are just for me, not shared with anyone else. It has been especially helpful in projects I work on sporadically. More on why a little later.

So, what drove me away from Git, exactly?

On the smallest projects, like game jam hacks, I just wanted to code. I didn't want to think about revisions and commit messages. I didn't need branching or merges. I didn't even need to rollback to another version, ever. I just …

Respect and Code Reviews

Code Reviews in a development team only function best, or possible at all, when everyone approaches them with respect. That’s something I’ve usually taken for granted because I’ve had the opportunity to work with amazing developers who shine not just in their technical skills but in their interpersonal skills on a team. That isn’t always the case, so I’m going to put into words something that often exists just in assumptions.
You have to respect your code. This is first only because the nature and intent of code reviews are to safeguard the quality of your code, so even having code reviews demonstrates a baseline of respect for that code. But, maybe not everyone on the team has the same level of respect or entered a team with existing review traditions that they aren’t acquainted with.
There can be culture shock when you enter a team that’s really heavy on code reviews, but also if you enter a team or interact with a colleague who doesn’t share that level of respect for the process or…

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. The only re…