Programming Python, Part I
A blog is not a blog if we can't add new posts, so let's do that:
>>> blog = blog + ["A new post."] >>> blog ['My first post', 'Python is cool', 'A new post.']
Here we set blog to a new value, which is the old blog, and a new post. Remembering all that merely to add a new post is not pleasant though, so we can encapsulate it in what is called a function:
>>> def add_post(blog, new_post): ... return blog + [new_post] ... >>>
def is the keyword used to define a new function or method (more on functions in structured or functional programming and methods in object-oriented programming later in this article). What follows is the name of the function. Inside the parentheses, we have the formal parameters. Those are like variables that will be defined by the caller of the function. After the colon, the prompt has changed from >>> to ... to show that we are inside a definition. The function is composed of all those lines with a level of indentation below the level of the def line.
So, where other programming languages use curly braces or begin/end keywords, Python uses indentation. The idea is that if you are a good programmer, you'd indent it anyway, so we'll use that indentation and make you a good programmer at the same time. Indeed, it's a controversial issue; I didn't like it at first, but I learned to live with it.
While working with the REPL, you safely can press Tab to make an indentation level, and although a Tab character can do it, using four spaces is the strongly recommended way. Many text editors know to put four spaces when you press Tab when editing a Python file. Whatever you do, never, I repeat, never, mix Tabs with spaces. In other programming languages, it may make the community dislike you, but in Python, it'll make your program fail with weird error messages.
Being practical, to reproduce what I did, simply type the class header, def add_post(blog, new_post):, press Enter, press Tab, type return blog + [new_post], press Enter, press Enter again, and that's it. Let's see the function in action:
>>> blog = add_post(blog, "Fourth post") >>> blog ['My first post', 'Python is cool', 'A new post.', 'Fourth post'] >>>
add_post takes two parameters. The first is the blog itself, and it gets assigned to blog. This is tricky. The blog inside the function is not the same as the blog outside the function. They are in different scopes. That's why the following:
>>> def add_post(blog, new_post): ... blog = blog + [new_post]
doesn't work. blog is modified only inside the function. By now, you might know that new_post contains the post passed to the function.
Our blog is growing, and it is time to see that the posts are simply strings, but we want to have a title and a body. One way to do this is to use tuples, like this:
>>> blog =  >>> blog = add_post(blog, ("New blog", "First post")) >>> blog = add_post(blog, ("Cool", "Python is cool")) >>> blog [('New blog', 'First post'), ('Cool', 'Python and is cool')] >>>
In the first line, I reset the blog to be an empty list. Then, I added two posts. See the double parentheses? The outside parentheses are part of the function call, and the inside parentheses are the creation of a tuple.
A tuple is created by parentheses, and its members are separated by commas. They are similar to lists, but semantically, they are different. For example, you can't update the members of a tuple. Tuples are used to build some kind of structure with a fixed set of elements. Let's see a tuple outside of our blog:
>>> (1,2,3) (1, 2, 3)
Accessing each part of the posts is similar to accessing each part of the blog:
>>> blog 'New blog' >>> blog 'This is my first post'
This might be a good solution if we want to store only a title and a body. But, how long until we want to add the date and time, excerpts, tags or messages? You may begin thinking you'll need to hang a sheet of paper on the wall, as shown in Figure 1, to remember the index of each field—not pleasant at all. To solve this problem, and some others, Python gives us object-oriented programming.
- You have to be careful there
7 weeks 3 days ago
- Wonder when LJ is going to
7 weeks 4 days ago
- Puerto Rico Free Software
7 weeks 5 days ago
7 weeks 6 days ago
- I hate voice commands
8 weeks 8 hours ago
- usabilty --- AGAIN with this nonsense
8 weeks 9 hours ago
- Don't make excuses
8 weeks 13 hours ago
- Sorry to let you know, but
8 weeks 14 hours ago
- Ridiculous statement. Not a
8 weeks 1 day ago
8 weeks 1 day ago