2.6, 3.0, and truly independent intepreters

[alex23]

On Oct 31, 2:05 am, "Andy O'Meara" <and... at gmail.com> wrote:
> I don't follow you there.  If you're referring to multiprocessing, our
> concerns are:
>
> - Maturity (am I willing to tell my partners and employees that I'm
> betting our future on a brand-new module that imposes significant
> restrictions as to how our app operates?)
> - Liability (am I ready to invest our resources into lots of new
> python module-specific code to find out that a platform that we want
> to target isn't supported or has problems?).  Like it not, we're a
> company and we have to show sensitivity about new or fringe packages
> that make our codebase less agile -- C/C++ continues to win the day in
> that department.

I don't follow this...wouldn't both of these concerns be even more
true for modifying the CPython interpreter to provide the
functionality you want?