Re: [Twisted-Python] making Screwtape (Tim Allen) a committer

2010-06-09 Thread Andrew Bennetts
Glyph Lefkowitz wrote:
> I think we should give screwtape an SVN account and make him an official
> reviewer.  He's been doing a lot of work on the distutils code which would be
> made easier by that, and he's been doing pretty decent reviews.

+1

I've been thinking (and occasionally saying) this for months!

-Andrew.


___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python


Re: [Twisted-Python] making Screwtape (Tim Allen) a committer

2010-06-09 Thread Thijs Triemstra | Collab
+2

On 10 Jun 2010, at 00:49, Kevin Horn wrote:

> +1
> 
> On Wed, Jun 9, 2010 at 5:25 PM, Glyph Lefkowitz  
> wrote:
> I think we should give screwtape an SVN account and make him an official 
> reviewer.  He's been doing a lot of work on the distutils code which would be 
> made easier by that, and he's been doing pretty decent reviews.
> 
> Thoughts?  (Feel free to voice any comments off-list, too.)
> ___
> Twisted-Python mailing list
> Twisted-Python@twistedmatrix.com
> http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
> 
> ___
> Twisted-Python mailing list
> Twisted-Python@twistedmatrix.com
> http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python


Re: [Twisted-Python] making Screwtape (Tim Allen) a committer

2010-06-09 Thread Tim Allen
On Wed, Jun 09, 2010 at 06:25:05PM -0400, Glyph Lefkowitz wrote:
> I think we should give screwtape an SVN account and make him an
> official reviewer.  He's been doing a lot of work on the distutils
> code which would be made easier by that, and he's been doing pretty
> decent reviews.

Well, this is a bit of a boost to the ol' ego. :D

The reason I've resisted asking for commit access before this is that
most of my efforts for Twisted have been either (a) things directly
useful for $EMPLOYER's Twisted deployments (such as the distutils
changes you mention), or (b) things indirectly useful for the purposes
of (a), such as cutting down the review queue to make it more likely
that my patches will be reviewed. While my non-work-related
contributions are non-zero, they're a lot less than my work-related
contributions.

That said, I've been following the Twisted project since (checks
mailing-list archive) October 2002, and I fully intend to keep
contributing reviews at the very least no matter who my employer is at
the time.

If you still think I'm a good candidate for committership, I'll happily
accept.


Tim "Screwtape" Allen

___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python


Re: [Twisted-Python] making Screwtape (Tim Allen) a committer

2010-06-09 Thread Kevin Horn
+1

On Wed, Jun 9, 2010 at 5:25 PM, Glyph Lefkowitz wrote:

> I think we should give screwtape an SVN account and make him an official
> reviewer.  He's been doing a lot of work on the distutils code which would
> be made easier by that, and he's been doing pretty decent reviews.
>
> Thoughts?  (Feel free to voice any comments off-list, too.)
> ___
> Twisted-Python mailing list
> Twisted-Python@twistedmatrix.com
> http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
>
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python


[Twisted-Python] making Screwtape (Tim Allen) a committer

2010-06-09 Thread Glyph Lefkowitz
I think we should give screwtape an SVN account and make him an official 
reviewer.  He's been doing a lot of work on the distutils code which would be 
made easier by that, and he's been doing pretty decent reviews.

Thoughts?  (Feel free to voice any comments off-list, too.)
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python


Re: [Twisted-Python] Dropping Python 2.4 support on Windows after 10.1

2010-06-09 Thread Glyph Lefkowitz

On Jun 9, 2010, at 6:04 PM, Ray Cote wrote:

> So, one positive vote for removing 2.4 support in Windows. 
> I prefer your Windows support be focused  moving forward to 2.7. 

Since Ray was the first sponsor of 2010, as well as a silver sponsor - see the 
AppropriateSolutions logo on the front page of twistedmatrix.com - everybody 
should read this as if it were spoken in a booming, disembodied voice emanating 
from Mount Olympus.  Goodbye, Windows 2.4 buildslaves! :-)

___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python


Re: [Twisted-Python] Dropping Python 2.4 support on Windows after 10.1

2010-06-09 Thread Ray Cote

We have quite a bit of Twisted/Windows code and it has all been ported over to 
2.5 or 2.6. 
I find it easier to upgrade Pythons on Windows since the bulk of our Windows 
products are shipped as py2exe containing their own interpreter. Cleaner than 
dealing with CentOS (for example) which has 2.4 in the base install. 

So, one positive vote for removing 2.4 support in Windows. 
I prefer your Windows support be focused  moving forward to 2.7. 

--Ray


- Original Message -
From: exar...@twistedmatrix.com
To: twisted-python@twistedmatrix.com
Sent: Wednesday, June 9, 2010 12:20:30 AM GMT -05:00 US/Canada Eastern
Subject: [Twisted-Python] Dropping Python 2.4 support on Windows after 10.1

Hey all,

I would like to propose that after Twisted 10.1 is released, we cease to 
claim support for Python 2.4 on any version of Windows.  This seems 
reasonable to me considering that Python 2.5 was first released in 
September of 2006 and that either Windows Python installations can be 
upgraded easily or very likely no upgrades are possible at all 
(specifically, no upgrades of Twisted).

The motivation for this is that we do not have the hardware resources to 
continue to test Twisted on Python 2.4 on Windows, particularly 
considering we will shortly want to begin testing on Python 2.7 on 
Windows.  If Windows/Python 2.4 support is important enough to anyone 
that they can offer to host the build slaves necessary to continue 
testing, then I'll withdraw the suggestion.

Lastly, I am not proposing dropping Python 2.4 support on any other 
platform (ie, Debian and Fedora).

Jean-Paul

___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

-- 
Ray Cote, President
Appropriate Solutions, Inc.
We Build Software
603.924.6079

___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python


Re: [Twisted-Python] Dropping Python 2.4 support on Windows after 10.1

2010-06-09 Thread Glyph Lefkowitz
On Jun 9, 2010, at 3:29 PM, Kevin Horn wrote:

> It would be nice to keep it if possible, but if it's a choice between a 
> buildslave for 2.4 and one for 2.7, then 2.7 really needs to take priority.

Well, you can make it possible by volunteering the hardware :).  I just don't 
think we should think about it for very long unless someone is willing to do 
that.
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python


Re: [Twisted-Python] Stackless.py and Twisted

2010-06-09 Thread Daniel Griffin
I dont know if twisted can really be counted as a scheduler. Its purpose is
more to do with nonblocking IO. To improve IO performance in stackless you
would need to add multiplexing to its scheduler(if it doesnt already have
it). http://eventlet.net/ seems to to this.

Dan

On Wed, Jun 9, 2010 at 9:22 AM, Andrew Francis wrote:

> Hi Folks:
>
> My talk "Prototyping Go's Select for Stackless with Stackless.py" recently
> got accepted to EuroPython. In the talk, I modified stackless.py to support
> the Go language's Select statement. I support Select as a method rather than
> a Python language feature. Implementing Select turns out to be relatively.
> However my original interest in stackless.py  was about subclassing the
> Twisted Reactor and making it stackless's scheduler. As opposed to running
> Twisted in a separate tasklet so an application does not deadlock under
> certain edge cases. In part I wanted to experiment with changing the
> stackless scheduler in such a way as to improve the performance of IO driven
> applications.  I am wondering if I would see a speed up if compiled into
> pypy-c (unfortunately right now I don't believe the JIT and Stackless are
> integrated)? Is this too wild an idea?
>
> Cheers,
> Andrew
>
>
>
>
>
>
> ___
> Twisted-Python mailing list
> Twisted-Python@twistedmatrix.com
> http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
>
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python


Re: [Twisted-Python] Dropping Python 2.4 support on Windows after 10.1

2010-06-09 Thread Konrads Smelkovs
Me 3. Existing apps wont likely care about new features and if they
need then upgrade to 2.5 is fully backwards compatible

2010/6/9, Glyph Lefkowitz :
>
> On Jun 9, 2010, at 12:20 AM, exar...@twistedmatrix.com wrote:
>
>> I would like to propose that after Twisted 10.1 is released, we cease to
>> claim support for Python 2.4 on any version of Windows.  This seems
>> reasonable to me considering that Python 2.5 was first released in
>> September of 2006 and that either Windows Python installations can be
>> upgraded easily or very likely no upgrades are possible at all
>> (specifically, no upgrades of Twisted).
>
> Seconded.

-- 
Nosūtīts no manas mobilās ierīces

--
Konrads Smelkovs
Applied IT sorcery.

___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python


Re: [Twisted-Python] Dropping Python 2.4 support on Windows after 10.1

2010-06-09 Thread Kevin Horn
On Tue, Jun 8, 2010 at 11:20 PM,  wrote:

> Hey all,
>
> I would like to propose that after Twisted 10.1 is released, we cease to
> claim support for Python 2.4 on any version of Windows.  This seems
> reasonable to me considering that Python 2.5 was first released in
> September of 2006 and that either Windows Python installations can be
> upgraded easily or very likely no upgrades are possible at all
> (specifically, no upgrades of Twisted).
>
> The motivation for this is that we do not have the hardware resources to
> continue to test Twisted on Python 2.4 on Windows, particularly
> considering we will shortly want to begin testing on Python 2.7 on
> Windows.  If Windows/Python 2.4 support is important enough to anyone
> that they can offer to host the build slaves necessary to continue
> testing, then I'll withdraw the suggestion.
>
> Lastly, I am not proposing dropping Python 2.4 support on any other
> platform (ie, Debian and Fedora).
>
> Jean-Paul
>
>
It would be nice to keep it if possible, but if it's a choice between a
buildslave for 2.4 and one for 2.7, then 2.7 really needs to take priority.

Kevin Horn
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python


Re: [Twisted-Python] Dropping Python 2.4 support on Windows after 10.1

2010-06-09 Thread Glyph Lefkowitz

On Jun 9, 2010, at 12:20 AM, exar...@twistedmatrix.com wrote:

> I would like to propose that after Twisted 10.1 is released, we cease to 
> claim support for Python 2.4 on any version of Windows.  This seems 
> reasonable to me considering that Python 2.5 was first released in 
> September of 2006 and that either Windows Python installations can be 
> upgraded easily or very likely no upgrades are possible at all 
> (specifically, no upgrades of Twisted).

Seconded.___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python


[Twisted-Python] Stackless.py and Twisted

2010-06-09 Thread Andrew Francis
Hi Folks:

My talk "Prototyping Go's Select for Stackless with Stackless.py" recently got 
accepted to EuroPython. In the talk, I modified stackless.py to support the Go 
language's Select statement. I support Select as a method rather than a Python 
language feature. Implementing Select turns out to be relatively. However my 
original interest in stackless.py  was about subclassing the Twisted Reactor 
and making it stackless's scheduler. As opposed to running Twisted in a 
separate tasklet so an application does not deadlock under certain edge cases. 
In part I wanted to experiment with changing the stackless scheduler in such a 
way as to improve the performance of IO driven applications.  I am wondering if 
I would see a speed up if compiled into pypy-c (unfortunately right now I don't 
believe the JIT and Stackless are integrated)? Is this too wild an idea?

Cheers,
Andrew




  

___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python