Comment on PEP-0238

[Emile van Sebille]

I'm sure this wouldn't be thread safe.  At this point, I wanted to get
something working that did what I expect.  I'm taking a look now to see how
this can work.


--

Emile van Sebille
emile at fenx.com

---------
"Robin Becker" <robin at jessikat.fsnet.co.uk> wrote in message
news:NjoSfiAYVXT7EweG at jessikat.fsnet.co.uk...
> In article <9iirju$j9rjr$1 at ID-11957.news.dfncis.de>, Emile van Sebille
> <emile at fenx.com> writes
> >
> >I've written a module that takes a few steps in the direction I'd like to
> >see things go, but even if that's not in the cards I'll probably use it
> >anyway.  It works like Tim's FixedPoint, but uses precision in a slightly
> >different way.  When run as __main__, it imports FixedPoint to compare
> >results as it tests.  Overall, this feels more like what I had in mind.
> >
> >Anyway, a sample session follows.  If anyone is interested in
testing/using
> >this, e-mail me and I'll send you back a copy.
> >
> >
> >Emile van Sebille
> >emile at fenx.com
> >
>
> how do these global class attributes work with threads? a lot of people
> are asking me about Zope (vis a vis reportlab) I keep telling them that
> reportlab isn't thread safe. I had imagined just packaging up all the
> module globals in some way and making things thread safe with a few
> locks.  Now I see that BNum.PRECISION is affecting all instances of the
> class, perhaps including someone else's thread so can BNum and similar
> be used in a real multithreaded environment like Zope?
>
>