Jan Erik Moström wrote:
>> Not sure it's what you're looking for, but are you aware of MoinX
>> (http://moinx.antbear.org)? It's a Twisted-based wiki packaged as
>> a standalone OS X app. Source is also available.
>
> Yep, but from what I understand it's would be the same as I set up
> any
Jack Jansen wrote:
> On 30-Mar-2007, at 22:55 , Kevin Walzer wrote:
>
>> Looking at the "Macintosh Library" documentation that ships with
>> 2.5, I
>> see a lot of outdated stuff: references to the old PythonIDE,
>> PackageManager, and so on. What is the process for updating these
>> docs,
>>
On 29 Mar, 2007, at 14:47, Nathan R. Yergler wrote:
> I have an application that I'd like to package using py2app, but I'm
> getting a little stuck with things. I *think* my problem is that my
> setup.py is fully setuptools-ized and my application script lives
> inside my package. Here's the ca
On 3/31/07, Ronald Oussoren <[EMAIL PROTECTED]> wrote:
>
> On 29 Mar, 2007, at 14:47, Nathan R. Yergler wrote:
>
> > I have an application that I'd like to package using py2app, but I'm
> > getting a little stuck with things. I *think* my problem is that my
> > setup.py is fully setuptools-ized an
On 31 Mar, 2007, at 5:41, Dethe Elza wrote:
> On 30-Mar-07, at 4:49 PM, Jack Jansen wrote:
>
>> Carbon itself should be fine. It is indeed undocumented within the
>> Python documentation, but the transformation from the official
>> Apple C documentation is pretty clear (I think).
>
> Is there any
On 31 Mar, 2007, at 1:49, Jack Jansen wrote:
On 30-Mar-2007, at 22:55 , Kevin Walzer wrote:
Looking at the "Macintosh Library" documentation that ships with
2.5, I
see a lot of outdated stuff: references to the old PythonIDE,
PackageManager, and so on. What is the process for updating the
Ronald Oussoren wrote:
> One thing we (Jack and I) talked about is moving at least the
> Carbon modules to its own separate project instead of being part of
> the standard library. The most important reason for this is that
> the Carbon modules and Python itself should be on a different
>
has wrote:
> For example, you could create a Mail rule that runs an 'AppleScript'
> action whenever new messages are received. That rule would load a
> PyOSA script and call its 'perform_mail_action_with_messages'
> function, passing it a list of message references. The script could
> then
Jacob Rus wrote:
> > For example, you could create a Mail rule that runs an 'AppleScript'
> > action whenever new messages are received.
>
> Could someone make such an example script (or something similar), and
> put it up somewhere?
There is a very simple example script included with PyOSA that
