R. David Murray <rdmur...@bitdance.com> added the comment: What appears to have happened is that the 2.5 maintenance release was branched *before* the release was cut, but Barry bumped the version of the email package after the branch and did not backport that bump to trunk. Between 2.5 and 2.6, email did not change significantly (just some bug fixes).
So, what we can do is bump the version to 4.0.2 in 2.6maint, and further bump it to 4.0.3 for 2.7 (where there is a behavior change from 4.0.2). Not perfect, but the best we can do. ---------- assignee: -> r.david.murray resolution: wont fix -> accepted stage: committed/rejected -> needs patch status: closed -> open type: -> behavior versions: +Python 2.6, Python 2.7 -Python 2.5 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue9085> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
