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

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

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

• Previous message: [Python-Dev] Addition of "pyprocessing" module to standard lib.
• Next message: [Python-Dev] Addition of "pyprocessing" module to standard lib.
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

> Apart from (1) and (2) which I think are unavoidable, nearly all the C
> code is Windows specific.  I assume you don't want to bring
> in the whole of pywin32 into stdlib...

I wouldn't structure it the same way as pywin32, but yes, I have
pondered exposing all of Win32 in a module, as part of the standard
library.

This has somewhat lost relevance with ctypes.

Regards,
Martin

• Previous message: [Python-Dev] Addition of "pyprocessing" module to standard lib.
• Next message: [Python-Dev] Addition of "pyprocessing" module to standard lib.
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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