[issue5843] Normalization error in urlunparse

2015-05-30 Thread Martin Panter
Changes by Martin Panter : -- resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> urllib.parse wrongly strips empty #fragment ___ Python tracker _

[issue5843] Normalization error in urlunparse

2015-02-08 Thread Martin Panter
Martin Panter added the comment: Looks like this duplicates Issue 22852, which has a patch, although its author had second thoughts on the implementation -- nosy: +vadmium ___ Python tracker ___

[issue5843] Normalization error in urlunparse

2014-10-09 Thread Aaron Hill
Aaron Hill added the comment: In order to fix this, I think ParseResult needs to have two additional fields, indicating with an empty prefix or query string are used. Both ParseResult.fragment and ParseResult.query omit the leading '#' or '?' from their value. This makes it impossible to deter

[issue5843] Normalization error in urlunparse

2014-09-30 Thread Mark Lawrence
Mark Lawrence added the comment: Slipped under the radar guys? -- nosy: +BreamoreBoy versions: +Python 3.4, Python 3.5 -Python 3.1, Python 3.2 ___ Python tracker ___ _

[issue5843] Normalization error in urlunparse

2010-11-02 Thread Éric Araujo
Changes by Éric Araujo : -- components: +Library (Lib) title: Possible normalization error in urlparse.urlunparse -> Normalization error in urlunparse versions: +Python 2.7, Python 3.1, Python 3.2 ___ Python tracker