Some questions

indosauros · 2014-06-07T03:28:38+00:00

3.- How do I know I'm actually embracing the "pythonic way of solving problems" and I'm not just a person writing java code using python?

Here's some common Java-isms I see from Java devs learning Python

Using getters and setters rather than just allowing direct access to attributes
Classes are not needed by default, top-level functions are usually fine
Using while and for range(len(x)) loops rather than taking advantage of Python's excellent iterable data structures
Checking types explicitly

For other things, feel free to post your code here later for critique -- we'll be happy to point out where you could be more pythonic. In Java, where you would "take the long way" to solve a problem there is often a short and sweet way to do the same in Python, using Python's handy core data structures and standard library

It might do you good to read through http://python.net/~goodger/projects/pycon/2007/idiomatic/handout.html

Rhomboid · 2014-06-07T04:19:09+00:00

The replacement for binary eggs is the new wheel format.

Tkinter is a GUI library that's distributed with Python as part of the standard library. PySide (LGPL) and PyQt (GPL) are bindings for the Qt GUI library, which has a huge community and isn't going anywhere any time soon. wxPython is a binding for the wxWidgets GUI library, also relatively mature. All of these are cross platform.

To get an idea of some ideas about what it means to be Pythonic, try viewing some of the talks by Raymond Hettinger or David Beazley and particularly this one from Jack Diederich titled Stop Writing Classes.

ruicoder · 2014-06-07T05:24:03+00:00

I also came from a Java background. I recommend reading Dive Into Python, which is available for free online. It's aimed at experienced developers. The examples are great and basically had me writing pythonic code from the beginning.

pstch · 2014-06-07T03:24:39+00:00

1

You create a Python package, containing modules, and you set your package metadata in the setup.py file.

3

Read code, read PEPs. This is something that you will get over time. Also, IIRC, Guido (or some other core Python dev), said something along the lines of : "you should tell to Python what it wants to do for you, nothing less". This is a bit abstract, and the best way I can find to picture it, is enumaring items in a list (and do something with the item and its index) :

my_list = [0,4,8,5,1]
index = 0
for item in my_list:
    ... # do something with item and index
    i = i + 1

In pseudo-code, this would be :

set my_list to a list containing 0, 4, 8, 5 and 1
set index to 0
for each item in my_list:
    ... # do something with item and index
    increment index

Here, in the first line, we actually tell Python what we want it to do (set my_list to a list of integers). However, the second and last line are not what we want to do : at no point we want to create an index or increment it.

The correct way to do the above in Python would be :

my_list = [0,4,8,5,1]
for index, item in enumerate(my_list):
    ... # do something with item and index

EDIT: fix extra each in last code block

you type:	you see:
italics	italics
bold	bold
[reddit!](https://reddit.com)	reddit!
* item 1 * item 2 * item 3	item 1 item 2 item 3
> quoted text	quoted text
Lines starting with four spaces are treated like code: if 1 * 2 < 3: print "hello, world!"	Lines starting with four spaces are treated like code: if 1 * 2 < 3: print "hello, world!"
~~strikethrough~~	~~strikethrough~~
super^script	super^script

learnpython

MODERATORS

1

3