On Mar 7, 2007, at 8:42 AM, Sidnei da Silva wrote:
> On Windows, the NT Service Controller does all the dirty job. And it's
> pretty easy to write a service in Python that can run any application.
> The simplest Python service is shorter than 30 lines I think.
Would such a controller:
- Invoke
Jim Fulton wrote:
>
> Having everything in one folder is great for development. It isn't so
> good for deployment, at least not on Unix.
Can you explain why? I do a lot of unix deployment, and the thought of a
buildout that sprays files all over the system, even if they are in
standard unix-
Rodrigo Senra wrote:
> For symmetry's sake in Windows a Python service manager could simply
> use SCManager API under the hood (through win32all) to get the job done,
> still keeping a consistent cross-platform modus operandi.
I would love to see this, particularly for Zope, although I sadly don't
Jim Fulton wrote:
> On Mar 5, 2007, at 4:38 PM, Phillip J. Eby wrote:
> ...
>> Personally, I don't care for the Paste Deploy syntax -- frankly
>> it's almost barbaric. :)
>
> I don't mean to pick on you, but I really *hate* comments like this.
That's okay ;-)
> criticism. I'd appreciate i
On 3/8/07, Chris Withers <[EMAIL PROTECTED]> wrote:
> I'm glad ZConfig exists.
Me too, though it does many things differently than if I'd had free reign.
> How does it handle nesting?
It doesn't, but an application can use explicit references to other
sections. It doesn't take care of things ma
On 3/8/07, Jim Fulton <[EMAIL PROTECTED]> wrote:
>
> On Mar 7, 2007, at 8:42 AM, Sidnei da Silva wrote:
>
> > On Windows, the NT Service Controller does all the dirty job. And it's
> > pretty easy to write a service in Python that can run any application.
> > The simplest Python service is shorter
> For symmetry's sake in Windows a Python service manager could simply
> use SCManager API under the hood (through win32all) to get the job done,
> still keeping a consistent cross-platform modus operandi.
That's what I do in UpLib. Works pretty well.
Bill
___
[ Chris Withers ]:
|I do a lot of unix deployment, and the thought of
|a buildout that sprays files all over the system, even if they are in
|standard unix-y location scares me a lot...
I am very sympathetic to the idea of keeping related thing together.
But I have some use cases (counter-exam
Chris Withers wrote:
> Jim Fulton wrote:
>> Having everything in one folder is great for development. It isn't so
>> good for deployment, at least not on Unix.
>
> Can you explain why? I do a lot of unix deployment, and the thought of a
> buildout that sprays files all over the system, even if
