[Python-Dev] email package status in 3.X

[Tres Seaver]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jesse Noller wrote:
> On Fri, Jun 18, 2010 at 4:48 PM, P.J. Eby <pje at telecommunity.com> wrote:
>> At 05:22 PM 6/18/2010 +0000, lutz at rmi.net wrote:
>>> So here it is: The prevailing view is that 3.X developers hoisted things
>>> on users that they did not fully work through themselves.  Unicode is
>>> prime among these: for all the talk here about how 2.X was broken in
>>> this regard, the implications of the 3.X string solution remain to be
>>> fully resolved in the 3.X standard library to this day.  What is a
>>> common Python user to make of that?
>> Certainly, this was my impression as well, after all the Web-SIG discussions
>> regarding the state of the stdlib in 3.x with respect to URL parsing,
>> joining, opening, etc.
> 
> Nothing is set in stone; if something is incredibly painful, or worse
> yet broken, then someone needs to file a bug, bring it to this list,
> or bring up a patch.

Or walk away.

> This is code we're talking about - nothing is set
> in stone, and if something is criminally broken it needs to be first
> identified, and then fixed.
> 
>> To be honest, I'm waiting to see some sort of tutorial(s) for using 3.x that
>> actually addresses these kinds of stdlib usage issues, so that I don't have
>> to think about it or futz around with experimenting, possibly to find that
>> some things can't be done at all.
> 
> I guess tutorial welcome, rather than patch welcome then ;)

The only folks who can write the tutorial are the ones who have already
drunk the koolaid.  Note that I've been making my living with Python for
about twelve years now, and would *like* to use Python3, but can't, yet,
and therefore haven't taken the first sip.

>> IOW, 3.x has broken TOOOWTDI for me in some areas.  There may be obvious
>> ways to do it, but, as per the Zen of Python, "that way may not be obvious
>> at first unless you're Dutch".  ;-)
> 
> What areas. We need specifics which can either be:
> 
> 1> Shot down.
> 2> Turned into bugs, so they can be fixed
> 3> Documented in the core documentation.

That's bloody ironic in a thread which had pointed at reasons why people
are not even considering Py3 for their projects:  those folks won't even
find the issues due to the lack of confidence in the suitability of the
platform.


Tres.
- --
===================================================================
Tres Seaver          +1 540-429-0999          tseaver at palladion.com
Palladion Software   "Excellence by Design"    http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkwc0I0ACgkQ+gerLs4ltQ6aDgCguYv+BXou0a42Yi7ERGCHOfIv
6REAnjejq4LDbE9c/gCqB+xs1yGfQ4KR
=/9fw
-----END PGP SIGNATURE-----