Message117160
| Author |
eric.araujo |
| Recipients |
belopolsky, benjamin.peterson, eric.araujo, facundobatista, gmattbond, loewis |
| Date |
2010年09月22日.23:28:43 |
| SpamBayes Score |
4.9340767e-09 |
| Marked as misclassified |
No |
| Message-id |
<1285198125.93.0.722642300008.issue9621@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
> When I was working with 2to3 this summer I was running it via python3,
> so I think the patch should work
Code in the patch uses print as a keyword (2.x), not a function (3.x). How does that work?
> however, if I've submitted it to the wrong place or the wrong branch,
> where should I be looking at to ensure my code does work on 3.2 and
> is submitted to the right place?
This tracker is the right place for bugs relevant to any CPython version. To ensure your code works on 3.2, just apply the diff on a 3.2 checkout. More info on http://www.python.org/dev/ (especially http://www.python.org/dev/patches/).
> In regard to the import gvgraph, I wasn't sure what to do with it
If the implicit relative import doesn’t work, as I suspect, sys.path.append(os.path.dirname(__file__)) should be enough.
(Cheers from a fellow GSoCer, by the way :) |
|