Hi,
I'm still loooking for a *GOOD* python2->python3 conversion guide for C
language modules.
Me too, but I haven't even found not so good ones yet.
I'd love to help on this (even if the only reason is selfish - I believe
pywin32 will *need* it while 2.x remains important.) Who would get
Issue 2847 - the aifc module still imports the cl module in 3.0.
Problem is that the cl module is gone. =) So it seems silly to have
the imports lying about. This can probably be changed to critical.
It shouldn't be a problem to rip everything cl-related out of aifc
Mike Klaas wrote:
> On 18-Jan-08, at 1:37 PM, Lars Immisch wrote:
>>
>> I like cmp, too. I've looked through my code, and I've only used it in
>> script-ish circumstances, but here is an example that sorts a list of
>> files by modification date:
>>
>
David A. Wheeler wrote:
> Bill Janssen:
>> I'm a bit baffled here; I find cmp() fairly handy in writing sort routines...
>> Is there a better / newer / official way of doing this? If not, isn't
>> "cmp()" still useful to have around?
>
> I agree with you - I find cmp() useful, and I notice that so
> That sounds like a nice basic simple interface. I suggest writing it up
> and submitting it as a patch or even making it stand alone module with
> its own distutils setup.py. It sounds like a good idea regardless of it
> its accepted into the standard library. (clearly what we have now for
Hi,
I recently worked on Python audio device support for Linux and OS X. Not
so recently, I wrote a DirectSound module for win32.
Python 2 has support for various audio devices, but they have no common
interface and some are broken or obsolete. Python 3000 might be a chance
to improve on this.
