I think a strong statement acknowledging how bad the original fuckup was and talking through this would help.
-
-
https://wiki.python.org/moin/PortingPythonToPy3k … also, why are Django's custom additions to six not upstreamed?
1 reply 0 retweets 1 like -
Replying to @wycats
according to the docs, their additions are for "internal use only" https://docs.djangoproject.com/en/1.10/topics/python3/#module-django.utils.six …
1 reply 0 retweets 1 like -
Replying to @eevee
right but the same shims would likely be useful for other projects, and help aid the transition.
2 replies 0 retweets 1 like -
still, that's not really an argument for the melodramatic assertion that py3k is Dead Man Walking
1 reply 0 retweets 0 likes -
I didn't agree with Zed, but I did say that the impression has solidified and *something* needs to change
1 reply 0 retweets 0 likes -
it's /been/ changing
2 replies 0 retweets 0 likes -
you have a news hook now, so it's a good time for a statement. As an outsider, I think a little humility would go a long way.
3 replies 0 retweets 3 likes -
You first. People who don't know what's going on but make grand failure pronouncements are main issue now.
1 reply 0 retweets 0 likes -
Replying to @ubernostrum @wycats and
Like seriously. Maybe trust the people in the trenches porting huge stuff. Because hi. We don't agree w/you.
1 reply 0 retweets 0 likes
sounds good. care to offer a new prediction?
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.