On Fri, Oct 2, 2009 at 12:14 PM, Valeriy Pogrebitskiy
wrote:
> Something can be done about that. One possible approach could be to use two
> argument lists (one - 'twistd' arguments, second - application's arguments)
> and enforce following rule(s):
>
As Jean-Paul mentioned, there is a ticket wh
On 04:14 pm, vpogr...@verizon.net wrote:
>Thank you!
>
>I still disagree with the following statement:
>>While this is a reasonable expectation, twistd does quite a lot and
>>it wouldn't be quite right to pass on all the arguments in a flat
>>list the way Python does.
>
>Something can be done abo
On Oct 2, 2009, at 12:14 PM, Valeriy Pogrebitskiy wrote:
I suggest that Twisted dev. team looks into implementing this...
Since we're telling other people how to spend their time...I suggest
that you supply a patch.
Thanks,
S
___
Twisted-Pytho
Thank you!
I still disagree with the following statement:
While this is a reasonable expectation, twistd does quite a lot and
it wouldn't be quite right to pass on all the arguments in a flat
list the way Python does.
Something can be done about that. One possible approach could be to
us
> I came across some problem using 'twistd' utility - that I would not
> have expected from it. The problem is - using 'twistd' to start
> application that requires command-line arguments. In other words, I
> would expect that 'twistd' passes command-line arguments to Python
> application - just as
On Thu, Oct 1, 2009 at 2:17 PM, Valeriy Pogrebitskiy
wrote:
> I came across some problem using 'twistd' utility - that I would not have
> expected from it. The problem is - using 'twistd' to start application that
> requires command-line arguments. In other words, I would expect that
> 'twistd' pa
I came across some problem using 'twistd' utility - that I would not
have expected from it. The problem is - using 'twistd' to start
application that requires command-line arguments. In other words, I
would expect that 'twistd' passes command-line arguments to Python
application - just as P
