[Python-Dev] Re: PEP 324 (process module)

Trent Mick trentm at ActiveState.com
Wed Aug 4 21:39:18 CEST 2004


[Peter Astrand wrote]
> > > Why not avoid threads on POSIX systems, and use select instead? My module
> > > does, although it does not provide an event-like IO interface.
> >
> > Because that wouldn't be cross-platform... perhaps it would be possible
> > though. I am not that experienced with select() -- I have generally
> > eschewed it because I can't use it on Windows as well.
> 
> The best way, IMHO, is to use select() on POSIX systems and threads on
> Windows. This is what my module does.

I'm willing to check that out for ProcessProxy. However, as I said, I
would be willing to remove ProcessProxy to a separate module (perhaps
just used by Komodo -- which was the original motivation for me) if it
is deemed not necessary/worthy for the core.


> I don't really see what we could gain from merging our modules.

One process control module to rule them all. Muwahahaha!
Seriously, I'd like to see "one obvious way to do it" for process
control in the core at some point (perhaps for Python 2.5) and my guess
is that a something between our two can provide it.

> What we have now is two different modules with two different APIs, and
> applications which uses these. If we were to merge our modules, then
> the API of either your, mine or both modules would have to change, which
> means that the applications using these would not work with the merged
> module.

I can change Komodo. And I don't use Twisted so I can break them.
(Muwahaha!)  ... more seriously I think a good final API (even if it
break backwards compat a little bit) is fine if the end result is a
better module for the core -- and as long as there is a __version__
attribute or something that users can key on.

Trent

-- 
Trent Mick
TrentM at ActiveState.com


More information about the Python-Dev mailing list