Pygame

[Terry Reedy]

"Alexander Rødseth" <alexanro at stud.ntnu.no> wrote in message
news:c5jgvh$2m5$1 at orkan.itea.ntnu.no...
> > What do you think should be the criteria for deciding whether
> > something "is part of Python" or isn't?
>
> I agree that my question was a bit vague, so here's a clarification:
> In that connection I meant "included in the standard installation
procedure
> for the average inexperienced user".


Things do not just get 'included in the standard installation procedure'
without someone doing the work to get it in and keep it working.  Python is
an all-volunteer operation.

For anything new to get added to the distribution, someone (usually the
project leader) must volunteer to write a PEP (if deemed necessary) or
otherwise lead and participate in a discussion of features, interface, and
implementation.  This may result in changes required for acceptance.  Then
the documentation and code must meet current standards.  Then there must be
a commitment to respond to bug reports for at least a few years.  And yes,
the package should be 'generally' useful and the best available.


Many package authors prefer to keep control of their own work.

Terry J. Reedy