I began by installing py-appscript like this:
macpro-administrators-computer:~ val$ sudo easy_install appscript
. . .
Finished processing dependencies for appscript
macpro-administrators-computer:~ val$
I thought that had worked, so I began the tutorial like this:
has wrote:
>
> As a long-term strategy for Python as a whole, sure. The above
> suggestion was for Kevin as a solution to his own more immediate needs.
>
Well, my commercial Python application isn't going to break tomorrow if
I don't remove the Carbon bits, but it seems the long-term tides a
On 3 Apr 2008, at 13:17, Ronald Oussoren wrote:
>
> On 1 Apr, 2008, at 22:09, has wrote:
>> On 1 Apr 2008, at 19:03, Kevin Walzer wrote:
>>
>>
>>> Yuk. Looks like I will have to remove the Carbon bits from my app at
>>> some point!
>>
>> Or just do what I did with appscript: fork off the bits you n
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
