I like to think of pylint as an expert system about how to write better Python. Some of the warnings are pointless (superfluous-parens really bugs me), but much of it is quite valuable. And for the -really- pointless stuff, you can create a pylintrc to ignore them forever. Personally, I prefer to add # pylint: disable=whatever for the warnings I'm willing to ignore, rather than create a pylintrc though.
Happily, Python is a very "googleable" language. You can probably just pick a project and start coding, and google your way out of any sticking points. You might also find some portions of http://stromberg.dnsalias.org/~strombrg/Intro-to-Python/ useful, perhaps especially the 2.x/3.x compatibility and common pitfalls. You might get something out of the one about generators too. HTH On Wed, Jul 30, 2014 at 1:20 PM, <guirec.cor...@gmail.com> wrote: > Hello, > > I am a Ruby developer and I want to program in Python. I know how to do > simple things like create classes, methods, variables and all the basics. I > want to know more. I want to know what is the Python philosophy, how to test, > how to create maintenable software, etc. > > I'm looking for online courses and any ressources I can have on the subject. > > Can you help me? > > Thanks, > Guirec Corbel. > -- > https://mail.python.org/mailman/listinfo/python-list -- https://mail.python.org/mailman/listinfo/python-list
