JP, what's the current state of the "insults" module you wrote? I'm
looking to bolt an ncurses-like client interface onto one of my
projects, and I didn't want to reinvent the wheel if it had already
been done, so some diligent searching turned up the "insults" module
you wrote.
There's almost no
On 08:46 pm, gl...@twistedmatrix.com wrote:
>
>On Oct 13, 2010, at 1:20 PM, James Y Knight wrote:
>>>Here's a compact version. The script uses OSX' Quartz to create and
>>>manipulate images. Twisted is used to wrap it as a webserver, images
>>>are served. More pointers on how to start and use it
On Oct 13, 2010, at 1:20 PM, James Y Knight wrote:
>> Here's a compact version. The script uses OSX' Quartz to create and
>> manipulate images. Twisted is used to wrap it as a webserver, images are
>> served. More pointers on how to start and use it in the script itself.
>
> You need to avoid
James,
On Oct 13, 2010, at 7:20 PM, James Y Knight wrote:
> You need to avoid using or importing any OSX APIs until after the
> daemonization has occurred. Unfortunately, twisted executes the entire script
> file before daemonizing. [that's unfortunate for other reasons besides this,
> too]
>
On Oct 13, 2010, at 12:05 PM, Erik van Blokland wrote:
>
> On Oct 13, 2010, at 5:52 PM, Phil Mayers wrote:
>
>> Other info indicates this is Apple trying to be clever and "protect"
>> applications from some signal handling issues surrounding fork() with
>> libraries which aren't safe in that
On Oct 13, 2010, at 5:55 PM, Phil Mayers wrote:
> Ah; apparently:
>
> http://developer.apple.com/library/ios/#documentation/cocoa/conceptual/Multithreading/AboutThreads/AboutThreads.html
>
> """using the fork function [...] Applications that depend on the Core
> Foundation, Cocoa, or Core Data
On 13/10/10 16:52, Phil Mayers wrote:
>
> If this really is true, then MacOS X is no longer posix-compliant in
> those circumstances, and Twisted is going to need some work :o(
One final note (sorry for the fragmentary posts!) - it seems the only
places Twisted calls fork() are in BaseProcess (ju
On 13/10/10 16:52, Phil Mayers wrote:
>
> If this really is true, then MacOS X is no longer posix-compliant in
> those circumstances, and Twisted is going to need some work :o(
>
> Can you share more details about the application; the context in which
> it is started, and which system libraries it'
On 13/10/10 16:40, Phil Mayers wrote:
> On 13/10/10 15:55, Erik van Blokland wrote:
>>
>> The code calls fork(), but no exec():
>
> fork() with no exec() is legal Unix.
>
> Various googling led me to:
>
> http://trac.adium.im/ticket/13976#comment:28
>
> """The problem is that OSX since version 10.6
On 13/10/10 15:55, Erik van Blokland wrote:
>
> The code calls fork(), but no exec():
fork() with no exec() is legal Unix.
Various googling led me to:
http://trac.adium.im/ticket/13976#comment:28
"""The problem is that OSX since version 10.6 (Snow Leopard) does NOT
allow processes launched via
Hi,
I'm running into crashes with deamonize() from _twistd_unix.py on OSX
10.6 "snow leopard".
Crash report contains the ominous flag:
USING_FORK_WITHOUT_EXEC_IS_NOT_SUPPORTED_BY_FILE_MANAGER
This flag shows up in some issues reported in other python projects on
OSX. Apparently 10.5 was mor
11 matches
Mail list logo
