Message166842
| Author |
pitrou |
| Recipients |
benjamin.peterson, christian.heimes, georg.brandl, meador.inge, ncoghlan, pitrou, python-dev, skrah, vstinner |
| Date |
2012年07月30日.01:02:56 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1343610038.3388.26.camel@localhost.localdomain> |
| In-reply-to |
<1343608704.26.0.651453151961.issue12834@psf.upfronthosting.co.za> |
| Content |
> This is especially so with Python 2.7 still having a couple of years
> of full maintenance left - that's a long time to leave it with a known
> broken memoryview implementation. I'm less worried about 3.2, since
> the upgrade path to 3.3 is easier in that case, but even that version
> is likely to see widespread use for a long time.
Well, there's a reason we don't backport features to bugfix branches,
especially when we're talking about a complete rewrite of the
implementation. So I really don't agree this should be backported. |
|