2009/11/9 Benjamin Peterson :
> 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.
Well, 2to3 is only plug
> data = "GIF89a(..."
>
> Is there a potentially automated path from where the code is today to
> something Python 3 (and 2to3) will like?
Not sure how you'll fix these; I personally always provided a b()
function that will do the right thing in both 2.x and 3.x. This can
get eventually repla
Guido> But if you're happy with only supporting 2.6, you can use b"..." and
Guido> the right thing will happen.
SpamBayes still supports 2.4...
Thanks for the feedback. I'll update the source manually, then run 2to3.
S
___
Python-Dev mailing
On Sun, Nov 8, 2009 at 5:48 PM, Benjamin Peterson wrote:
> 2009/11/8 :
>>
>> 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
>>
2009/11/8 :
>
> 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 ne
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
