> I really wish there was a way to fold these two trackers into one
> repository. Sometimes all I have is a number and I don't know whether
> it's a bug or patch. AFAIK, there's no overlap between ids for
> patches and bugs. If you get /that/ working, I'd be your best friend.
That would require a CGI script that tries both and sees which one
doesn't return an error. I think it's overkill.
Here are two scripts I recently started using:
sfpatch --------------------------------------------------------------
#! /usr/bin/env python
import os, sys, webbrowser
def main():
args = sys.argv[1:]
if len(args) != 1:
print "usage: %s patchno" % sys.argv[0]
sys.exit(2)
url = "http://python.net/crew/mwh/py/bug/" + args[0]
webbrowser.open(url)
main()
sfbug ----------------------------------------------------------------
#! /usr/bin/env python
import os, sys, webbrowser
def main():
args = sys.argv[1:]
if len(args) != 1:
print "usage: %s patchno" % sys.argv[0]
sys.exit(2)
url = "http://python.net/crew/mwh/py/patch/" + args[0]
webbrowser.open(url)
main()
----------------------------------------------------------------------
Is it worth to check these into Tools/demos/scripts/?
--Guido van Rossum (home page: http://www.python.org/~guido/)
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4