Welcome to Python in general and SeaPIG in particular, Mike. When Ben talks about "setting up your machine", I'm guessing he's talking about getting all the ancillary things that help with Python development. Pip <http://pypi.python.org/pypi/pip> is one such tool. It's a Python specific library manager that allows you to quickly install additional libraries to help with particular tasks. It's like the package manager on a Linux desktop, but designed specifically around Python packages distributed at the Python Package Index <http://pypi.python.org/pypi>. Another useful tool is virtualenv <http://pypi.python.org/pypi/virtualenv>. Virtualenv allows you to have multiple python "environments", each with its own set of libraries and completely isolated from one another. It's a lifesaver when you have two projects which each require different, incompatible versions of the same library. A third such tool would be your editor. It seems like you're comfortable with vim, so you should be set as far as that goes. This link <http://www.sontek.net/blog/detail/python-with-a-modular-ide-vim> goes over a set of vim plugins that will help you be more productive as a Python programmer. It's nothing that you'll need right away, but if you choose to stick with Python, the plugins and configuration described there will make your day-to-day programming easier. Finally, Flake8<http://pypi.python.org/pypi/flake8>is an automatic tool that performs static analysis of your code to find possible bugs and ensures that your code is formatted according to PEP 8<http://www.python.org/dev/peps/pep-0008/>conventions. There's a vim plugin <https://github.com/nvie/vim-flake8>, too, so you can even get instant feedback on your style and possible errors as you write.
As far as immediate action items go, I'd suggest becoming familiar with PEP 8, first. It defines how Python code is expected to look, and what conventions other developers will be expecting your code to adhere to. In addition, most Python code out there (unless it's quite old) follows PEP 8 convention, so understanding PEP 8 will help you when you're reading code as well. Anyway, welcome to Python! -- Rohit Patnaik On Mon, Sep 17, 2012 at 12:22 AM, Mike Malveaux <[email protected]>wrote: > Thanks, everyone, for the warm welcome and interesting links. I'll > definitely be exploring those over time. > > I had been wondering whether to learn Python 2, 3, or both. I had thought > to do both, but now it sounds like Py 3 should be my priority. Python 2 is > installed by default with the Linux system I'm using (Ubuntu 10.04 LTS, > 'Lucid Lynx' -- not thrilled with the Unity interface, so I'm > procrastinating about upgrading this box), and downloaded and installed > Python 3. I have noticed some syntax differences, even with the beginner > exercises I've done. > > Ben, I'm not sure mean about "setting up your machine." Is it more than > installing Python? > > iPython looks interesting. I've just installed it, and will begin playing > around with it. > > As for text editors -- when I'm forced to work in Windows, like when I'm > helping my girlfriend with a project for her job, I use NoteTab. (Arggh! > I just realized, she no longer has administrative permissions on her new > computer. I guess I'll have to go back to Notepad. Luckily for me, most > of the help she needs is with Excel.) On Linux, I use Kate or Vim most of > the time. > > What is the pip tool? > > Again, thanks everyone for your kind help. > > All the best, > Mike M. / Tacoma > > On Sun, Sep 16, 2012 at 6:26 PM, Ben Racine <[email protected]> wrote: > >> I'm of the opinion that setting up your machine is a huge first step in >> exploring python. I am happy to point you to some resources when you are >> ready for that. >> >> I'd say the first three steps on that front are getting used to iPython, >> finding a text editor you can learn to like (I can recommend sublimetext), >> and perhaps learning the pip tool so that you can grab 3rd part libraries >> quickly. >> >> These are all just opinion, but I think knowing your tools will greatly >> help you be able to explore the concepts you will be reading about. >> >> Sent from my iPad >> >> On Sep 15, 2012, at 10:54 PM, Mike Malveaux <[email protected]> >> wrote: >> >> Hi folks, the subscription confirmation asked for an intro, so here goes. >> >> My name is Mike. I live in Tacoma. I'm not really a programmer -- my >> last job was Snowboard Instructor, and for years before that I drove and >> dispatched trucks -- but circumstances have convinced me that learning to >> program is a Good Thing. But, which language first? >> >> The sources I've seen that I like best indicate that BASIC is no longer >> considered the best program for newbies (nor for anything else, >> apparently). But Python seems to be well recommended for neophytes, and >> looks like it will do most or maybe all of the web scripting stuff I want >> to do down the road. >> >> So, here I am! I've begun working my way through the tutorial document >> at http://docs.python.org/tutorial and I'm looking forward to see you >> kind folks in person, probably next month. Probably 90% of the discussion >> will go whizzing over my head, so I promise to listen more than I speak. >> >> All the best, >> Mike M. / Tacoma >> >> >
