l...@rmi.net writes:
> FWIW, after rewriting Programming Python for 3.1, 3.x still feels
> a lot like a beta to me, almost 2 years after its release.
Email, of course, is a big wart. But guess what? Python 2's email
module doesn't actually work! Sure, the program runs most of the
time, but e
David and his Google Summer of Code student, Shashwat Anand.
You can read Shashwat's weekly progress updates at http://l0nwlf.in/ or
subscribe to http://twitter.com/l0nwlf for more micro updates.
We have more than 30 paid students working on Python 3 tasks this year, most
of them participating un
Barry Warsaw wrote:
> On Jun 16, 2010, at 08:48 PM, l...@rmi.net wrote:
>
>> Well, it looks like I've stumbled onto the "other shoe" on this
>> issue--that the email package's problems are also apparently
>> behind the fact that CGI binary file uploads don't work in 3.1
>> (http://bugs.python.org
2010/6/17 Bill Janssen :
> There's a related meta-issue having to do with antique protocols.
Can I know what meta-issue are you talking about exactly?
> FTP, for instance, was designed when the Internet had only 19 nodes connected
> together with custom-built refrigerator-sized routers. A very
On Thu, Jun 17, 2010 at 08:43, Barry Warsaw wrote:
> On Jun 16, 2010, at 08:48 PM, l...@rmi.net wrote:
>
>>Well, it looks like I've stumbled onto the "other shoe" on this
>>issue--that the email package's problems are also apparently
>>behind the fact that CGI binary file uploads don't work in 3.1
Nick Coghlan wrote:
> My personal perspective is that a lot of that code was likely already
> broken in hard to detect ways when dealing with mixed encodings -
> releasing 3.x just made the associated errors significantly easier to
> detect.
I have to agree with this, and not just about encoding
On Jun 16, 2010, at 08:48 PM, l...@rmi.net wrote:
>Well, it looks like I've stumbled onto the "other shoe" on this
>issue--that the email package's problems are also apparently
>behind the fact that CGI binary file uploads don't work in 3.1
>(http://bugs.python.org/issue4953). Yikes.
>
>I trust
I.e. even with the change, it would *still* depend on objimpl.h
(and other) settings what ABI this debug DLL exactly has.
I think it does. My proposal was perhaps not clear: For existing
python versions, always export _PyObject_DebugMalloc et al.
Hmm. That's still not clear. What are "exist
