Bastien Léonard

I've pushed the changes on Github. Hopefully someone can test it on Windows before I make a new source release, but I understand it's not practical to build the project...

Well, I guess I managed to fuck up the rc-compatible branch again. This error means that there's another key constant that was wrongly declared. Cython couldn't find the constant in...

Just did some more testing, and yeah I still get crashes in some cases. I'll try to fix that ASAP, for lack of a more precise estimation...

Damn, a month already. :( Good thing you reminded me. I found how to fix it, expect a release tomorrow.

I just pushed the fix on both branches. Hopefully someone can test it before I upload a release tomorrow. Otherwise I'll still try to upload it, since it's a pretty...

I reopen this, so that I don't forget it in the future. By the way, is seems very dangerous to support deepcopy: it means that the user could easily duplicates...

As I said, I can't think of one good for duplicating heavy objects like images. That's already a good reason for not supporting it, in my opinion. The fact that...

I have added `copy()` methods in some classes: Sprite, Time, Transform, FloatRect and IntRect (Vector2f already had one). So far, I don't see how deep copy support would be useful...

What would an image deep copy provide that a normal doesn't? `Image` doesn't hold a reference to any Python object, so it should be the same. `Sprite` has a reference...

I haven't tried it yet, but I know Sonkun made an example for his binding: http://openhelbreath.net/python-sfml2/examples/pyqt4.html Apparently, he ported the X11 function that's needed: https://github.com/Sonkun/python-sfml2/blob/master/src/sfml/x11.pyx Personally, I would rather avoid...