> > I see the magic cookies as a poor man's (but more compatible!) version
> > of a chain of importers as advocated by Greg Stein and other imputil
> > fans. [...]
> I know this has been asked before, but cannot recall
> any of the arguments against it: how about replacing
> Jack's magic cookies with importer objects?
For the record: I definitely agree with both comments here. The only thing
that would need solving (but maybe it already is? Greg?) is the external
representation of an importer, as I'd definitely want to be able to name them
in PYTHONPATH (or the mac equivalent).
Jack Jansen | ++++ stop the execution of Mumia Abu-Jamal ++++
Jack.Jansen(a)oratrix.com | ++++ if you agree copy these lines to your sig ++++
www.oratrix.nl/~jack | see http://www.xs4all.nl/~tank/spg-l/sigaction.htm
It looks like there has been some mail glitch that result in no
digests being sent between 11/26 and 12/01 and no messages being
archived between 11/24 and 12/01. Does anyone keep a personal archive
that has those messages? I'd like to read them.
On Wed, 1 Dec 1999, Geoffrey Furnish wrote:
> Well, like I said above, I haven't analyzed your posts for technical
> details, so I can't say whether you made avoidable mistakes. But I
> definitely do agree with you that it is roughly 100 times harder than
> it needs to be, to use Python from C++. The charter of this sig is to
> fix that, by developing the additional software that would allow
> Python's compiled interface to be exploited from C++ "with ease".
> The first and most basic issue, is compiling Python so it initializes
> C++ global objects correctly. There is a patch on the sig's www site
> to help with that.
Any opinions from this esteemed body re: integrating said patch in the
My first Python-Dev post. :-)
>We had some discussion a while back about enabling thread support by
>default, if the underlying OS supports it obviously.
What's the consensus about Python microthreads -- a likely candidate
for incorporation in 1.6 (or later)?
Also, we have a couple minor convenience functions for Python in an
MSDEV environment, an exposure of OutputDebugString for writing to
the DevStudio log window and a means of tripping DevStudio C/C++ layer
breakpoints from Python code (currently experimental). The msvcrt
module seems like a likely candidate for these, would these be
Origin Systems, Inc.