2009/11/8 <skip at pobox.com>: > > SpamBayes has several files which contain raw 8-bit data embedded in > string literals. Before I do manual work to make them parseable by 2to3 > I thought I would ask if there was either a fixer available which I'm > not getting by default or if there is an opportunity to add a new fixer > to 2to3. > > The usage is pretty straightforward. For example, a string literal > might contain the bytes for a GIF image: > > data = "GIF89a(..." > > Is there a potentially automated path from where the code is today to > something Python 3 (and 2to3) will like? Not to my knowledge. I would prefer to not add a fixer for this directly to 2to3 because it is not correct for most programs. However, I think 2to3 should grow some sort of plugin system, so custom fixers can easily be written and used. -- Regards, Benjamin
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