Archive for the ‘coding’ Category

Global Python Sprint Weekend in São Paulo

Thursday, May 8th, 2008

This weekend (May 10th and 11th) will happen the Global Python Sprint Weekend. Like the last PythonBugDay our Python User Group (GruPy-SP) will meet to work together.

This time our meeting will be held at Universidade de São Paulo IME (Instituto de Matemática e Estatística) thanks to RBP and the CCSL (Free Software Competence Centre) =)

Other Python User Groups from Brazil are also meeting to work together, check the wikipage for the PythonBugDay to know if there will be a meeting near you :-) (or you can work from your home sweet home).

Python friends meeting

Monday, May 5th, 2008

Last Friday, me, Luciano Pacheco and Marcelo Honório went to Pedro Werneck‘s house (or werneck’s cave) to talk, eat and, of course, code python :-)

We wrote a small guide (portugues only, sorry… I promise i’Il translate it to English) about preparing the environment for those who want to participate of the PythonBugDay (or even for the curious who want to play with the cpython code).

Of course I’ve worked on my GSoC project implementing the new (2.5) “defaultdict” object (in the collections module), but this is subject of another post :-)

Werneck and Pacheco also worked on some issues/bugs listed in the CPython bugtracker and I’ve introduced them to PyPy (and vice-versa hehe).

After all this coding we ate Japanese food and our friend Andrews suggested a new kind of development method, Sushi-Driven Development… nice! :)

FLISOL 2008 – Python Talk

Saturday, May 3rd, 2008

Last Saturday I gave a Python talk at FLISOL 2008 in Sào Paulo. The public was students who were learning programming (C and Visual Basic), so it was a very basic talk. The event was great and so was the talk, the only problem was that I thought that the public would be programmers with some experience, but not really. Anyway, the FATEC students seemed to like Python and some of then came to talk to me after the event to know more about the language and to ask where they could find more information!

I’ll upload my presentation somewhere.

I’ve helped to install GNU/Linux (Ubuntu) on a FATEC lab, people there were very nice!

Well, I felt like my “mission” was accomplished :-)

FLISOL 2008 in São Paulo – Python Talk

Friday, April 25th, 2008

I’ll give a talk about Python in FLISOL 2008 São Paulo. It’s scheduled to start at 15h00. It’s a basic talk for people who code in other languages and don’t know much about Python.

Take a look here for more information about FLISOL.

PyPy 2.5 features: __hash__ behavior

Thursday, April 24th, 2008

One small change in Python 2.5 is the __hash__ method behavior. In earlier versions the __hash__ method was supposed to return a normal integer always, but now due to changes in the id() builtin function the __hash__ method behavior was changed and it can return a long or an int.

This was easy to change in PyPy, the hash() builtin function implementation is part of the ObjectSpace as almost all the builtin functions and types.

It’s in pypy/objspace/descroperation.py:

def hash(space, w_obj):
        w_hash = space.lookup(w_obj, '__hash__')
        if w_hash is None:
            if space.lookup(w_obj, '__eq__') is not None or \
               space.lookup(w_obj, '__cmp__') is not None:
                raise OperationError(space.w_TypeError,
                                     space.wrap("unhashable type"))
            return default_identity_hash(space, w_obj)
        w_result = space.get_and_call_function(w_hash, w_obj)
        if space.is_true(space.isinstance(w_result, space.w_int)):
            return w_result
        else:
            raise OperationError(space.w_TypeError,
                     space.wrap("__hash__() should return an int or long"))

One don’t even need to know PyPy well to understand that the lines

if space.is_true(space.isinstance(w_result, space.w_int)):
    return w_result
else:
    raise OperationError(space.w_TypeError,
             space.wrap("__hash__() should return an int or long"))

are responsible for raising a TypeError when the returning value from __hash__ is not an integer.

So just changing the condition

space.is_true(space.isinstance(w_result, space.w_int)):

to

(space.is_true(space.isinstance(w_result, space.w_int)) or
 space.is_true(space.isinstance(w_result, space.w_long))):

will solve this, I hope!

But that’s not all the code needed, I promised Carl to write tests for everything, but as I like to use TDD (test-driven development) it was already done.

Oh, and should I mention that I love PyPy’s documentation? Thanks guys!

FISL 9.0 – GameJam and OLPyC Genius

Thursday, April 24th, 2008

At FISL 9.0 occurred the second OLPC GameJam Brasil (if you don’t know what is GameJam, take a quick look here). The difference from the GameJam occurred in São Carlos is this time we were inside FISL, an event with more than 7,000 people attending and not in a nice and peaceful laboratory :-)

Together with all this people there were lots of interesting talks going on simultaneously and a lot of nice people to talk to. Because of this “details” we started coding whit only 6 hours left for the deadline :-)

This GameJam with me were Andrews Medina and Luciano Pacheco, I met both from Python Brasil community (on PyConBrasil last year). We decided to develop a “Genius” clone for the XO, using it’s special “game-keys” and the “tablet position”. With only 6 hours to develop a game you can imagine that we were not even thinking about the graphics at all, but, suddenly a nice guy named came and offered himself to make pictures for our game. It happens that the guy was Valéssio Brito and he is an “Inkscape genius” (sorry… :P ), in less than one hour he made some cool graphics. That re-excited us and we went on with our code (less than one hour left for the deadline).

At 20h05, five minutes after the deadline, we finished the game, installed it in XO and send to the organization. It was very nice and as Pacheco said, it was one of the best experiences I could do in FISL for me :D

I must say that Andrews was shaking (like a “vara verde” as Luciano said) at the time we delivered our game… :P

Valéssio, me, Andrews and Luciano
From left to right: Valéssio, me (with the XO), Andrews and Pacheco

Thanks Pacheco, Andrews and Valéssio, it was very nice to participate :-)

Thanks to the LEC/UFRGS people that organized the GameJam and thanks to the PyGame folks becuase they’ve developed this wonderful library :-)

Supporting Python 2.5 features in PyPy – GSoC 2008

Tuesday, April 22nd, 2008

As you probably know my GSoC proposal to work on PyPy interpreter, supporting the Python 2.5 features, has been accepted. This post is a short explanation of my Google Summer of Code project.

PyPy

The PyPy project aims at producing a flexible and fast Python implementation. The guiding idea is to translate a Python-level description of the Python language itself to lower level languages. Rumors have it that the secret goal is being faster-than-C which is nonsense, isn’t it?

PyPy is divided into the python interpreter and the translator framework. The interpreter is written in RPython (a subset of Python) and the main goal is to provide an easy-to-hack (for python programmers ;) ) Python interpreter.

PyPy’s interpreter currently supports only a few features introduced in Python 2.5, like __index__ (for slicing) and some part of the ‘with’ statement. Also, the 2.5 changes to the language and to the standard library have not been ported yet (although some have been, like the ctypes).

Goal

This proposal idea is to bring Python 2.5 features and changes to PyPy interpreter, this includes porting the modules and writing code for the features it self.

Here are some of the features I’ll work on:

  • PEP 308: Conditional Expressions[*]
  • 328: Absolute and Relative Imports
  • PEP 342: New Generator Features
  • PEP 343: The with statement[*]
  • PEP 352: Exceptions as New-Style Classes

[*] part of this features are already supported by PyPy

Benefits

With support to 2.5 features and changes more the PyPy interpreter will be up-to-date so people who wants to use this features can be happy using PyPy. This probably means more people using PyPy (i hope!) :-)

Why this project?

The first reason I’ve chosen the PyPy project is that I really like their ideas and goals. I was looking for collaborating to it in some way for a long time, but it took me some time to read the docs and to really understand the project.

As I like PyPy ideas and I’m starting to plan my graduation project/bachelor’s thesis, my work on PyPy interpreter will be a big part of it. Maybe I can explain my ideas in another post :-)

I would like to thank Google (and the SoC folks), Python Software Foundation, PyPy and specially to Carl Friedrich Bolz* who will be my GSoC mentor and Leonardo Santagada who helped me to understand PyPy and to write my application.

* morepypy is a blog where PyPy developers talk to the community, it’s not Carl’s personal blog.

Thanks to my friends from Python Brasil community too.

Approved in GSoC

Monday, April 21st, 2008

As mentioned before I’ve applied to GSoC to work on PyPy for the Python Software Foundation.

Today I’m very happy to say that my project got approved and I will work on PyPy interpreter the next three months. It means that a lot of PyPy posts are coming, and the first one will be a introduction to the project, what is PyPy, the interpreter and the translation framework :)

Stay tuned if you are interested in PyPy! Congratulations to everybody that have applied to GSoC this year =)

Google Summer of Code 2008: deadline for applications extended

Monday, March 31st, 2008

For those who were thinking to apply to GSoC, good news and no more excuses, the student applications open and deadline have been extended by one week. The deadline now is Monday – Jan 7th.

If you are applying, stay tunned to the official calendar and good luck!

V GruPy meeting – March, 24 – Report

Monday, March 31st, 2008

The GruPy-SP (São Paulo Python User Group) March meeting happened at Google’s office in São Paulo. The meeting was attended by about 60 people and we had 5 talks. This was a very special meeting because we had talks from Guido, Alex Martelli, Collin Winter and Cary Hull (all by video conference).

Talks:

  • Rodolpho Eckhardt – “PyCon 2008 Trip Report” – Rodolpho made a very nice report of his experience going to Chicago to attend PyCon 2008. It certainly made some of us think about going to PyCon 2009.
  • Cary Hull – “Divmod’s Axiom” – Cary Hull talked about the Axiom ORM, it was a fast talk introducing it features and benefits.
  • Alex Martelli – “Callback design patterns” – Very good technical talk. Details about the use and implementation of Callbacks.
  • Guido van Rossum – “Python 3000″ – Probably the talk that everyone was waiting, It was the same talk that Guido made at PyCon 2008, he showed the main changes that will happen in Python 3000 and what to do to be prepared to change your code from Python 2.x to 3000.
  • Collin Winter – “2to3″ – Very good talk from Collin Winter about how the 2to3 conversion tool works, where it does and where it doesn’t work.

The next meeting will be held on May. We will not have a meeting in April because of FISL (Free Software International Forum) that will happen on April 17th, 18th and 19th at Porto Alegre.

Thanks to everyone who attended, specially to Rodolpho who organized the meeting.