CNRI vs. BeOpen (was Re: Splitting c.l.py...)

[Tim Peters]

[Aahz Maruch]
> I think what would be interesting is to know what effect this is having
> on Python (e.g. is it delaying 1.6?).

Yes.  1.6 schedule and workload details are still in negotiation.

> It would also be nice to know if there is an ETA for getting all
> this resolved.

As CNRI's Dr. Kahn said in the "Python release delay" message Guido
forwarded on Friday, "As soon as these [issues] are resolved, which we hope
will be very shortly".  This is all we know now.

> It would be useful to know what parts of the Python community are
> affected;  I notice, for example, that starship.python.net still says
> to send checks for PSA to CNRI -- is that correct?

The PSA is hosted by CNRI, so definitive answers about the PSA will have to
come from them.  I'm not trying to be coy here, I simply don't know!
Yesterday Jeremy suggested that email to webmaster at python.org may be your
best shot at contacting CNRI, and I don't know of a better way
(webmaster at python.org goes to CNRI personnel, not to anyone at BeOpen
PythonLabs).

> (My interest in the last question comes mainly because I'm getting ready
> to upload my thread tutorial to a web site, and I'd prefer to use a
> Python site rather than my own.)

Don't worry about that!  Everyone would love to have your thread tutorial,
and we'll find a Pythonic home for it no matter what.  It's just that before
the divorce decree is final, nobody can know where all the kids will live.

patience-is-a-virtue-even-on-the-internet-ly y'rs  - tim