We definitely should have some lint-type tool that we put into the commit hook to automatically show errors/warning. I'm not sure which one is best suited for our purpose, ideally something with some flexibility to adapt it to our needs.
On Thursday, January 31, 2013 9:37:18 AM UTC, Harald Schilly wrote: > > On Wednesday, January 30, 2013 7:10:46 PM UTC+1, Travis Scrimshaw wrote: >> >> Should we be encouraging (or enforce) new code to be python 3 >> compliant? In particular, not using removed syntax such as exceptions as >> `raise ExceptionType, args` or `<>` comparisons? >> > > Are there any intentions to use Python's "pep8" to sanitize Sage code? For > other projects, I started to use pep8 and autopep8 to format the code. It > has a very long list of rules and checks them for the source code files. > For the entire Sage library this might be not a good idea, but file-by-file > we might try to use it to spot these irregular code lines. I know, that > pep8 complains about "<>" and other things, e.g. "is not" vs. "!=" and so > on. I don't know about the raise/except thing, once could try it … > > H > -- 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 sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
