[Tracker-discuss] Patch tracking

anatoly techtonik techtonik at gmail.com
Sat Nov 24 23:24:37 CET 2012


On Sat, Nov 24, 2012 at 7:04 AM, Ezio Melotti <ezio.melotti at gmail.com>
 wrote:

> Thanks for your work!
>
> I played a bit with the code tonight and used it to create a json that
> maps filename -> list of issues with a patch that affects that filename.
>

Nice. Is it possible to add this lookup to the post commit hook script to
report about amount of patches available for files that had been committed?
It is much easier to review code that's already in your mind.

I made a simple page to filter the results and uploaded it here for now:
> http://wolfprojects.altervista.org/issues.html
> It requires javascript and it's a bit slow (at least on my pc), but it
> allows you to enter a module name or path and it will list all the issues
> related to the files that match the search (regex search should also work).
> This is still a work in progress though.
> If you want you can find the json at
> http://wolfprojects.altervista.org/files.json


Good work. I've pulled all the changes, but now I am getting:

Traceback (most recent call last):
  File "modstats.py", line 142, in <module>
    print('#%s: %s' % (issuen, issue['title']))
  File "C:\Python27\lib\encodings\cp437.py", line 12, in encode
    return codecs.charmap_encode(input,errors,encoding_map)
UnicodeEncodeError: 'charmap' codec can't encode character u'\u2019' in
position 65: character maps to <undefined>


Path cleaning is a good thing. Good auto classification also needs some
rules that needs additional data:
  - detect full path from just filename
    - if path is unknown, analyse filename
      - if filename is unique in Python source tree, return it's path
      - if filename is not unique, compare parent path components
recursively
        - if not successful, try context match patch
        - if everything fails, choose the first one
          - if it fails also, maintain manual connection patch <---> file
  For that to work we need an index of Python source code directory tree.

And add % of recognized patches.
With manual classification (triaging) it is possible to keep this per-cent
at 100.

BTW, what kind of license do you prefer? I didn't mention it first, but
it's better to set this early. I am for public domain with some credits
file at the top.
-- 
anatoly t.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/tracker-discuss/attachments/20121125/213e01b5/attachment.html>


More information about the Tracker-discuss mailing list