On 1 Apr, 2008, at 22:09, has wrote:
On 1 Apr 2008, at 19:03, Kevin Walzer wrote:
What does the "de-Macification" in Python 3.0 mean? Will the Carbon
modules be removed?
I've found the answer to my own question:
http://www.python.org/dev/peps/pep-3108/
Yuk. Looks like I will have to remove
On 1 Apr, 2008, at 17:37, Kevin Walzer wrote:
has wrote:
With the general de-Macification of Python 3.0 being planned, I
wonder
if the python3.0 interpreter should take the same approach, leaving
it
up to individual modules to decide if and when they want a GUI
connection? Anyone any tho
On 1 Apr 2008, at 19:03, Kevin Walzer wrote:
>> What does the "de-Macification" in Python 3.0 mean? Will the Carbon
>> modules be removed?
>
> I've found the answer to my own question:
>
> http://www.python.org/dev/peps/pep-3108/
>
> Yuk. Looks like I will have to remove the Carbon bits from my
On 1 Apr 2008, at 16:22, Ronald Oussoren wrote:
>> With the general de-Macification of Python 3.0 being planned, I
>> wonder
>> if the python3.0 interpreter should take the same approach, leaving
>> it
>> up to individual modules to decide if and when they want a GUI
>> connection? Anyone any
On 1 Apr 2008, at 16:37, Kevin Walzer wrote:
> What does the "de-Macification" in Python 3.0 mean? Will the Carbon
> modules be removed?
See:
http://www.python.org/dev/peps/pep-3108/
I'm totally for their removal from the 3.0 stdlib, btw. They did their
job in the day, but they've
Kevin Walzer wrote:
>
> What does the "de-Macification" in Python 3.0 mean? Will the Carbon
> modules be removed?
>
I've found the answer to my own question:
http://www.python.org/dev/peps/pep-3108/
Yuk. Looks like I will have to remove the Carbon bits from my app at
some point!
--
Kevin W
has wrote:
>
> With the general de-Macification of Python 3.0 being planned, I wonder
> if the python3.0 interpreter should take the same approach, leaving it
> up to individual modules to decide if and when they want a GUI
> connection? Anyone any thoughts?
What does the "de-Macification"
On 1 Apr, 2008, at 14:23, has wrote:
On 1 Apr 2008, at 13:19, has wrote:
The command line python interpreter automatically upgrades to a full
GUI process whenever OS APIs linked to the Window Manager are
called. [...]
As an addendum:
Note that this isn't an issue with Ruby as the ruby inte
On 1 Apr 2008, at 13:19, has wrote:
> The command line python interpreter automatically upgrades to a full
> GUI process whenever OS APIs linked to the Window Manager are
> called. [...]
As an addendum:
Note that this isn't an issue with Ruby as the ruby interpreter only
upgrades to a GUI
On 29 Mar 2008, at 09:11, Alex MacCaw wrote:
> Thanks - that works.
> I'm wondering how to get rid of the python rocket ship that appears
> in the dock when I start sending applescript events. I've tried
> deleting the object reference to app('Finder') but to no avail.
The command line pytho
10 matches
Mail list logo
