This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: Version number inconsistency in email package
Type: behavior Stage: resolved
Components: Library (Lib) Versions: Python 2.7, Python 2.6
process
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: r.david.murray Nosy List: eric.araujo, l0nwlf, orsenthil, r.david.murray, tkikuchi
Priority: normal Keywords:

Created on 2010-06-26 07:27 by tkikuchi, last changed 2022-04-11 14:57 by admin. This issue is now closed.

Messages (10)
msg108688 - (view) Author: Tokio Kikuchi (tkikuchi) Date: 2010-06-26 07:27
Python 2.6 email version number is 4.0.1 while that of py2.5 is 4.0.2.
Clearly, py2.6 email is newer and should have higher number.
msg108705 - (view) Author: Shashwat Anand (l0nwlf) Date: 2010-06-26 10:57
In python2.5 email version is 4.0.2
In python2.6 email version is 4.0.1
In python 2.7rc2 email version is 4.0.2

I think version number is wrong with 2.5, it should have been 4.0.0 rather than 4.0.2.

David: Adding you as nosy so as you can confirm upon this.
msg108708 - (view) Author: Senthil Kumaran (orsenthil) * (Python committer) Date: 2010-06-26 11:11
I doubt we would care about changing the version number in Python 2.5.
Python 2.5 *might be* only in Security Fix mode and this does not
qualify for a change in Python 2.5. So, just leave it as it is and
don't rely on the version number is in the answer.
msg108739 - (view) Author: R. David Murray (r.david.murray) * (Python committer) Date: 2010-06-26 18:38
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.
msg108741 - (view) Author: R. David Murray (r.david.murray) * (Python committer) Date: 2010-06-26 19:09
Bumps committed in r82246 and r82257.
msg108811 - (view) Author: Tokio Kikuchi (tkikuchi) Date: 2010-06-28 00:28
I filed this bug because I found email 4.0.2 in Python 2.5 was not suitable for the latest mailman 2.1.13 especially for Japanese environment.  It would be best if you can further bump the Python 2.6 email to 4.0.3 and that of 2.7 to 4.0.4. (Or, 5.0.1 if there is significant change in the behaviour.)
Than you.
msg108816 - (view) Author: R. David Murray (r.david.murray) * (Python committer) Date: 2010-06-28 02:11
So you are saying that there are significant differences between the 2.5 email and the 2.6 email?  Can you give any details?
msg108818 - (view) Author: Tokio Kikuchi (tkikuchi) Date: 2010-06-28 06:00
I couldn't track down the bug but the symptom is that python 2.5 -- mailman 2.1.13 combination make Japanese message 'mojibake'.  Using only email package for generating message cause no trouble as far as I can check, so the bug may be in mailman (with combination of python 2.5).
msg124492 - (view) Author: Éric Araujo (eric.araujo) * (Python committer) Date: 2010-12-22 08:24
If there is no further discussion, I’d say the original bug is fixed anc this report should be closed.
msg124505 - (view) Author: R. David Murray (r.david.murray) * (Python committer) Date: 2010-12-22 13:23
It's too late to make any further changes in version numbers for 2.x.  Sorry this slipped by me.
History
Date User Action Args
2022-04-11 14:57:02adminsetgithub: 53331
2010-12-22 13:23:36r.david.murraysetstatus: open -> closed
nosy: orsenthil, tkikuchi, eric.araujo, r.david.murray, l0nwlf
messages: + msg124505
2010-12-22 08:24:00eric.araujosetnosy: + eric.araujo
messages: + msg124492
2010-06-28 06:00:29tkikuchisetmessages: + msg108818
2010-06-28 02:11:46r.david.murraysetstatus: closed -> open

messages: + msg108816
2010-06-28 00:28:56tkikuchisetmessages: + msg108811
2010-06-26 19:09:52r.david.murraysetstatus: open -> closed
resolution: accepted -> fixed
messages: + msg108741

stage: needs patch -> resolved
2010-06-26 18:38:14r.david.murraysetstatus: closed -> open

assignee: r.david.murray
versions: + Python 2.6, Python 2.7, - Python 2.5
messages: + msg108739
type: behavior
resolution: wont fix -> accepted
stage: resolved -> needs patch
2010-06-26 11:12:26orsenthilsetstatus: open -> closed
resolution: wont fix
stage: resolved
2010-06-26 11:11:00orsenthilsetnosy: + orsenthil
messages: + msg108708
2010-06-26 10:57:32l0nwlfsetnosy: + r.david.murray, l0nwlf

messages: + msg108705
versions: + Python 2.5, - Python 2.6
2010-06-26 07:27:54tkikuchicreate