[issue1500504] Alternate RFC 3986 compliant URI parsing module

2014-12-31 Thread Berker Peksag
Changes by Berker Peksag : -- nosy: +berker.peksag versions: +Python 3.5 -Python 3.4 ___ Python tracker ___ ___ Python-bugs-list mai

[issue1500504] Alternate RFC 3986 compliant URI parsing module

2014-12-31 Thread A.M. Kuchling
Changes by A.M. Kuchling : -- nosy: -akuchling ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.

[issue1500504] Alternate RFC 3986 compliant URI parsing module

2013-11-12 Thread A.M. Kuchling
A.M. Kuchling added the comment: Here's a slightly modified version of urischeme.py that can be run under Python 3 and compares its results with urllib.parse, printing out the mismatches. The major differences seem to be 1) urischeme fills in the default port if it's not explicitly provided, e

[issue1500504] Alternate RFC 3986 compliant URI parsing module

2013-08-29 Thread Martin Panter
Changes by Martin Panter : -- nosy: +vadmium ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue1500504] Alternate RFC 3986 compliant URI parsing module

2013-05-30 Thread Łukasz Langa
Changes by Łukasz Langa : -- nosy: +lukasz.langa ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.

[issue1500504] Alternate RFC 3986 compliant URI parsing module

2012-11-18 Thread Ezio Melotti
Changes by Ezio Melotti : -- versions: +Python 3.4 -Python 3.2 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue1500504] Alternate RFC 3986 compliant URI parsing module

2010-11-03 Thread Nick Coghlan
Nick Coghlan added the comment: Just to be clear, even *I* don't think adding urischemes as it stands is a particularly great idea, and I wrote it. The only reason I haven't closed the issue is because I'd like to see it mined for additional tests in test_urlparse and perhaps even implementat

[issue1500504] Alternate RFC 3986 compliant URI parsing module

2010-11-03 Thread Éric Araujo
Éric Araujo added the comment: Sure, adding tests is a no-brainer. Regarding the module, I’m a bit reluctant. I see value in providing low-level building blocks (think OS calls) and high-level utilities for regular use, but here it seems that urllib.parse and urischemes are at the same level

[issue1500504] Alternate RFC 3986 compliant URI parsing module

2010-11-02 Thread Nick Coghlan
Nick Coghlan added the comment: I still like the higher level API concept, although I might not do it exactly as presented here any more. Independently of introducing a new parsing API, it would be worthwhile extracting the parsing tests from the attached module to make sure the *existing* p

[issue1500504] Alternate RFC 3986 compliant URI parsing module

2010-11-02 Thread Éric Araujo
Éric Araujo added the comment: Is this still relevant? Can’t the improvements make it into urllib.parse? -- nosy: +eric.araujo ___ Python tracker ___

[issue1500504] Alternate RFC 3986 compliant URI parsing module

2010-08-08 Thread Terry J. Reedy
Changes by Terry J. Reedy : -- versions: +Python 3.2 -Python 2.7, Python 3.1 ___ Python tracker ___ ___ Python-bugs-list mailing lis

[issue1500504] Alternate RFC 3986 compliant URI parsing module

2010-07-10 Thread Nick Coghlan
Nick Coghlan added the comment: "accepted" is a little too strong for the current status of this :) I've removed the easy tag as well (making the case for this or something like it in the standard library it going to involve a fair bit of effort - the coding was actually the comparatively eas

[issue1500504] Alternate RFC 3986 compliant URI parsing module

2010-07-10 Thread Senthil Kumaran
Senthil Kumaran added the comment: A new way for parsing URI. I have not reviewed it even after saying I would like to, but having the dependency issue resolved, I think it is good to look at it again, especially if it leads some helpful approaches to parsing IRI. -- assignee: -> ors

[issue1500504] Alternate RFC 3986 compliant URI parsing module

2009-04-22 Thread Senthil
Senthil added the comment: I am willing to review this/work on it. But I wonder if this can be categorized as easy task. 1) Integration to Standard Library will involve compatibility with existing parsing, which will invariably involve certain tweaks (with discussions/buy-in from others). 2) T

[issue1500504] Alternate RFC 3986 compliant URI parsing module

2009-04-22 Thread Daniel Diniz
Daniel Diniz added the comment: ISTM that gathering the issues where this would help is a good start, but I haven't had the time to do it yet. -- dependencies: +URI parsing library ___ Python tracker ___

[issue1500504] Alternate RFC 3986 compliant URI parsing module

2009-04-22 Thread Nick Coghlan
Nick Coghlan added the comment: The code itself is no longer the hard part here (hence the easy tag). The problem is the fact that getting something like this into the standard library is a tough sell on python-dev because it isn't really a field tested module, but once people start downloading

[issue1500504] Alternate RFC 3986 compliant URI parsing module

2009-04-22 Thread Senthil
Changes by Senthil : -- nosy: +orsenthil ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.o

[issue1500504] Alternate RFC 3986 compliant URI parsing module

2009-04-22 Thread Daniel Diniz
Changes by Daniel Diniz : -- keywords: +easy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue1500504] Alternate RFC 3986 compliant URI parsing module

2009-03-20 Thread Daniel Diniz
Daniel Diniz added the comment: I'll collect open issues that would be solved by this. -- components: +Library (Lib) -None nosy: +ajaksu2 stage: -> patch review type: -> feature request versions: +Python 2.7, Python 3.1 ___ Python tracker