On 2016-04-21 10:33, Jeroen Demeyer wrote: > Hello, > > concerning the porting of Sagelib(*) to Python 3, I propose to > eventually add > > from __future__ import print_function, division, absolute_import, > unicode_literals > > to *every* .py(x) file in Sagelib (even those modules which don't print, > don't divide, don't import and don't have literals). The reason is twofold: > - whenever we add such a future import, we force new code to use > printing/division/imports/literals compatible with Python 3. > - adding the future import serves as documentation that a particular > module has been ported to Python 3, at least for the aspects which the > future statements enforce. > > We obviously do not have to add all these imports all at once, we can > gradually add them while we port code to Python 3. I already added a few > __future__.division imports while I was porting some divisions. > > What do you think?
+1 What about doctests? Manually add these import there everywhere? Or is there a "better way"? Daniel -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
