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.
Archive for April, 2008
FLISOL 2008 in São Paulo – Python Talk
Friday, April 25th, 2008FLISOL 2008 in São Paulo
Thursday, April 24th, 2008Time to install free software 
FLISOL, the Latin-America Free Software Installfest (Festival Latinoamericano de Instalação de SOftware Livre) will happend this Saturday, 04/26, simultaneously in more than 20 countries in Latin America.
In São Paulo it will be held at FATEC Zona Sul, R. Frederico Grotte, 353 – Jd São Luís.
Our schedule:
Installfest
09:00 – 18:00
Talks:
10:00 – 12:00
Free Software and Security
Rodrigo Montoro
Workshops
09:00 – 11:00
Desenvolvendo em C com GTK
Alex Marcio Ribeiro Nunes
13:00 – 16:00
Shell Script
Edegar C. Berlezzi
More information at http://www.flisol.org.br (portuguese) and http://installfest.info/ (spanish and portuguese).
If you live in São Paulo, I hope to see you there
PyPy 2.5 features: __hash__ behavior
Thursday, April 24th, 2008One 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, 2008At 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… 
), 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 
I must say that Andrews was shaking (like a “vara verde” as Luciano said) at the time we delivered our game…
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, 2008As 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, 2008As 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 =)
FISL 9.0 – 1. São Paulo -> Porto Alegre -> FISL!
Sunday, April 20th, 2008There isn’t words to describe how I’m happy after this 3 days in Porto Alegre, attending to FISL. I’ll try to make a report of what happened, but it’s so much things that I’ll post it in parts.
So this is part one, and it starts at the São Paulo international airport (at Guarulhos-SP) on April 17th. Destination: Porto Alegre, Rio Grande do Sul!
With me were my two friends Marcelo Honório and David Kwast. Our flight was scheduled to leave at 4h30am. Well, it left exactly 4h25am, after one hour flying they announced that the Porto Alegre airport was closed due to bad weather conditions, and worse, all near airports were closed so went back to São Paulo international airport. We had to wait until 11am, when the Porto Alegre aiport opened again and all flights that were late started to leave.
After that we finally did it and went to PUC (the university where FISL happened) but what happened there is history for the next post, the first day report
FISL 9.0 – here we go again!
Tuesday, April 15th, 2008I’m attending to FISL 9.0, the Fórum Internacional Software Livre (or Free Software International Forum) that happens every year in Porto Alegre, Rio Grande do Sul – Brazil, organized by the Brazilian Free Software Association (Associação Software Livre – ASL) and Projeto Software Livre – PSL-BR. I think FISL doesn’t need any introduction at all, it’s a well known and recognized event around the world.
This is the second time I’m going, the first was last year and I was very impressed about the organization, people and talks. It’s a very good chance to meet people that I talk only through mailing lists
This FISL (9.0) is very special for the Brazilian Python community, it’s our first FISL as an association (APyB, Associação Python Brasil/Python Brazil Association) and we already have an exclusive track (called APyB, see the FISL program). In the program you can see the APyB track and the “Development: Python” track, both are about Python talks, but the first was given to APyB by FISL organization, the APyB had 10 slots where it could choose the talks and this talks doesn’t need to pass through the FISL evaluation process.
Is there any reason to think that this isn’t the “Python @ FISL” year?
I hope everybody have a nice FISL!
See you at Porto Alegre!
![PythonBrasil[7]](http://www.python.org.br/banners-pythonbrasil/pythonbrasil7-rectangle.gif)