Hi Phillip,
On Mon, Jun 12, 2006 at 12:29:48PM -0400, Phillip J. Eby wrote:
> This idea would address the needs of external maintainers (having a single
> release history) while still allowing Python developers to modify the code
> (if the external package is in Python's SVN repository).
It's a
On 6/12/06, Phillip J. Eby <[EMAIL PROTECTED]> wrote:
> At 09:04 AM 6/12/2006 -0700, Guido van Rossum wrote:
> >IOW I think PEP 360 is an unfortunate historic accident, and we would
> >be better off without it. I propose that we don't add to it going
> >forward, and that we try to get rid of it as
At 09:04 AM 6/12/2006 -0700, Guido van Rossum wrote:
>IOW I think PEP 360 is an unfortunate historic accident, and we would
>be better off without it. I propose that we don't add to it going
>forward, and that we try to get rid of it as we can.
4 of the 6 modules in PEP 360 were added to Python in
On 6/11/06, Phillip J. Eby <[EMAIL PROTECTED]> wrote:
> As requested in PEP 360, please inform me of any issues you find so they
> can be corrected in the standalone package and merged back to the trunk.
>
> I just wasted time cutting an 0.1.1 release of the standalone wsgiref
> package only to fin
