A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2008-May/079594.html below:

[Python-Dev] Addition of "pyprocessing" module to standard lib.

[Python-Dev] Addition of "pyprocessing" module to standard lib.Bill Janssen janssen at parc.com
Tue May 20 03:13:11 CEST 2008
> On Mon, May 19, 2008 at 5:15 PM, Bill Janssen <janssen at parc.com> wrote:
> >> If you can run a pure Python module
> >> that does not depend on any C extension, then that platform has the
> >> support needed to run Python.
> >
> > This is certainly a point of view.  One that many end-users wouldn't
> > understand :-).
> 
> Perhaps, but it's clear-cut. Is OS X not properly supported because it
> can't run the _winreg module? I just don't like labeling a platform as
> unsupported just because ctypes doesn't compile on it.

I assume _winreg runs everywhere Python is said to run, and there's a
Windows registry to examine, so I think it's a different kettle of
fish.  ctypes doesn't run everywhere Python is said to run, and there
are dynamic libraries to call into.

I think it would be great if we could get some AIX, HP-UX, and Solaris
boxes for Thomas to work on.  What would motivate IBM, H-P, and Sun to
donate such gear?  Perhaps each of the companies have an office
somewhere that could help with this resource allocation?  For
instance, talking to the "AIX Collaboration Center" of IBM
(aixcc at us.ibm.com)?

And these are all SYSV derivatives, aren't they?  So perhaps it's some
common fix for all three?

Bill
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4