Windows Porting Questions

[Mark Young]

(More questions likely to follow as I work through the tests)

Currently, the daemon test fails as the _on_daemonize function in
daemon.py uses fork, which of course isn't available on windows. With
the current design, I don't see how to replace the fork calls with
anything from multiprocessing.

It seems to me that daemon is a fairly important component to get
working, but I don't currently know how to fix it.

Does anyone have any suggestions or do we just accept and document
that Daemon is unsupported on windows at the present time?

[James Mills]

Hey Mark,

Simple solution is to document as unsupported on Windows;

skip the test and delete the Component.

The alternative is to implement a Win32Service Component

however I feel that's an exercise for someone more experience

with Windows API Programming and probably not something

we're willing to support in an official capacity as we have no

licensed access to Windows platforms.

cheers

James

James Mills / prologic

E: prol...@shortcircuit.net.au

W: prologic.shortcircuit.net.au

--
You received this message because you are subscribed to the Google Groups "circuits" group.
To post to this group, send email to circuit...@googlegroups.com.
To unsubscribe from this group, send email to circuits-user...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/circuits-users?hl=en.

[Mark Young]

Okay. Thanks. I'd like to fix this properly later, but I'll just mark
it as unsupported for now.

[James Mills]

Well there's no Daemon(s) on Windows :)

Just Windows Services :)

cheers

James

James Mills / prologic

E: prol...@shortcircuit.net.au

W: prologic.shortcircuit.net.au

On Thu, Dec 27, 2012 at 5:26 AM, Mark Young <mark...@gmail.com> wrote:

Okay. Thanks. I'd like to fix this properly later, but I'll just mark
it as unsupported for now.