These modules are deprecated and have been removed in Python 3.x

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

These modules are deprecated and have been removed in Python 3.x

Leo-2
On this page: http://docs.python.org/library/mac.html, so what replace
these removed modules?

Thanks.

Leo

_______________________________________________
Pythonmac-SIG maillist  -  [hidden email]
http://mail.python.org/mailman/listinfo/pythonmac-sig
unsubscribe: http://mail.python.org/mailman/options/Pythonmac-SIG
Reply | Threaded
Open this post in threaded view
|

Re: These modules are deprecated and have been removed in Python 3.x

Kevin Walzer-5
On 4/18/12 9:44 AM, Leo wrote:
> On this page: http://docs.python.org/library/mac.html, so what replace
> these removed modules?
>
> Thanks.
>
> Leo

Nothing did, really. Those modules are legacy ones dating back to the
days of OS 9, and were automatically generated from the Carbon
framework's headers by a tool (bgen) that few understood a decade ago
and no one understands today. Many of the functions are not 64-bit, and
untangling that would be a nightmare.

There are various ways to get at the functionality that these modules
offered: use PyObjC; use other functions from the standard library,
since these functions pre-date OS X running on top of Unix; or, if you
are really in need of specific functionality offered by one of the
Carbon modules, code your own C wrapper library or use Ctypes.

--
Kevin Walzer
Code by Kevin
http://www.codebykevin.com
_______________________________________________
Pythonmac-SIG maillist  -  [hidden email]
http://mail.python.org/mailman/listinfo/pythonmac-sig
unsubscribe: http://mail.python.org/mailman/options/Pythonmac-SIG
Reply | Threaded
Open this post in threaded view
|

Re: These modules are deprecated and have been removed in Python 3.x

Leo-2
On 2012-04-18 22:00 +0800, Kevin Walzer wrote:

> Nothing did, really. Those modules are legacy ones dating back to the
> days of OS 9, and were automatically generated from the Carbon
> framework's headers by a tool (bgen) that few understood a decade ago
> and no one understands today. Many of the functions are not 64-bit,
> and untangling that would be a nightmare.
>
> There are various ways to get at the functionality that these modules
> offered: use PyObjC; use other functions from the standard library,
> since these functions pre-date OS X running on top of Unix; or, if you
> are really in need of specific functionality offered by one of the
> Carbon modules, code your own C wrapper library or use Ctypes.

Thank you for this information.

Leo

_______________________________________________
Pythonmac-SIG maillist  -  [hidden email]
http://mail.python.org/mailman/listinfo/pythonmac-sig
unsubscribe: http://mail.python.org/mailman/options/Pythonmac-SIG