Two bugs fixed in pull request 91: * The latest commit fixes a urlparse issue that was introduced in December 2010 which makes the command-line unusable for any Python < 2.6. This fix is not exactly elegant, though -- It adds a 2.4 compatible urlparse.py file, and imports it instead if an incompatible urlparse is imported. * https://github.com/eode/dulwich/commit/0baed03424ca1bc774e926bccbdc48b1a88fc4f4 * The commit previous to that fixes the 2.4 compatibility issues specific to my earlier patch. * https://github.com/eode/dulwich/commit/7e4f29aaa1bdcdd97200130cd088895b74f0fee2
Both of the above patches are included in my pull request: https://github.com/jelmer/dulwich/pull/91
urlparse bug introduced Dec 2010: https://github.com/jelmer/dulwich/commit/6eb98037b4970642bb307f4c1c8eae702f46c746 Note usage of parsed.scheme, parsed.port, parsed.username, etc.
Two bugs fixed in pull request 91: /github. com/eode/ dulwich/ commit/ 0baed03424ca1bc 774e926bccbdc48 b1a88fc4f4 /github. com/eode/ dulwich/ commit/ 7e4f29aaa1bdcdd 97200130cd08889 5b74f0fee2
* The latest commit fixes a urlparse issue that was introduced in December 2010 which makes the command-line unusable for any Python < 2.6. This fix is not exactly elegant, though -- It adds a 2.4 compatible urlparse.py file, and imports it instead if an incompatible urlparse is imported.
* https:/
* The commit previous to that fixes the 2.4 compatibility issues specific to my earlier patch.
* https:/
Both of the above patches are included in my pull request: /github. com/jelmer/ dulwich/ pull/91
https:/
urlparse bug introduced Dec 2010: https:/ /github. com/jelmer/ dulwich/ commit/ 6eb98037b497064 2bb307f4c1c8eae 702f46c746
Note usage of parsed.scheme, parsed.port, parsed.username, etc.