[Python-porting] Possible bug: Using futurize, code blows up around line 271 in main.py
Guido van Rossum
guido at python.org
Mon Sep 22 18:25:15 CEST 2014
More information about the Python-porting mailing list
Mon Sep 22 18:25:15 CEST 2014
- Previous message: [Python-porting] Possible bug: Using futurize, code blows up around line 271 in main.py
- Next message: [Python-porting] Possible bug: Using futurize, code blows up around line 271 in main.py
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi Mark, You probably want to file a bug report with the futurizer's project. Try the issue tracker there (if I understand the project you're using): https://github.com/PythonCharmers/python-future/issues Thanks for reporting! On Fri, Sep 19, 2014 at 1:38 PM, Mark Richardson <mrichardson3 at gmail.com> wrote: > Greetings all, > > It's my first post, so if I'm breaking protocol, please forgive. Tried > running futurize on > some of my old python2 code and the futurizer blew up around line 271 with > error: > > NameError: name 'logger' is not defined > > The original line starts with > > logger.info('Output ... > > and I think it should be > > logging.info('Output ... > > First off, I'm not sure if this is what the author intended and secondly, > if it is what the author intended, what is the method that I go about to > see > that the bug gets corrected? I'm perfectly fine, with fixing my own copy > to get it to run, but it seems like I should generate a resolution to the > source > code so that the next guy/gal doesn't have to go down the same rabbit > hole. If there's a link to a rtfm page for these type of issues, I'm more > than > happy to read it and reapply my issue again. > > > Thanks, > Mark R. > > > _______________________________________________ > Python-porting mailing list > Python-porting at python.org > https://mail.python.org/mailman/listinfo/python-porting > -- --Guido van Rossum (python.org/~guido) -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-porting/attachments/20140922/535b0b04/attachment.html>
- Previous message: [Python-porting] Possible bug: Using futurize, code blows up around line 271 in main.py
- Next message: [Python-porting] Possible bug: Using futurize, code blows up around line 271 in main.py
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-porting mailing list