Sorry for the lame-ass bug report, but my stack is really deep and I didn't
want this one to go unreported. I just tried 0.6c10 to see if it would fix a
problem I'm having. How fortunate that it hit Cheeseshop at just the right
time ;). Unfortunately, there's a bug in
At 03:33 PM 10/19/2009 -0400, Barry Warsaw wrote:
Sorry for the lame-ass bug report, but my stack is really deep and I didn't
want this one to go unreported. I just tried 0.6c10 to see if it would fix a
problem I'm having. How fortunate that it hit Cheeseshop at just the right
time ;).
On Oct 19, 2009, at 3:55 PM, P.J. Eby wrote:
At 03:33 PM 10/19/2009 -0400, Barry Warsaw wrote:
Sorry for the lame-ass bug report, but my stack is really deep and
I didn't
want this one to go unreported. I just tried 0.6c10 to see if it
would fix a
problem I'm having. How fortunate that it
On 2009-10-19, at 2055, P.J. Eby wrote:
Thanks; it's fixed and pushed back to PyPI.
With the same version number. What about the people who have already
installed your broke 0.6c10 that don't read this list?
Matt
___
Distutils-SIG maillist -
At 02:05 AM 10/20/2009 +0100, Matthew Wilkes wrote:
On 2009-10-19, at 2055, P.J. Eby wrote:
Thanks; it's fixed and pushed back to PyPI.
With the same version number. What about the people who have already
installed your broke 0.6c10 that don't read this list?
They'll see an announcement
