Python 3 compatibility about fuckitpy HOT 11 CLOSED

If you do get it working and submit a pull request, I'll be happy to take a look.

from fuckitpy.

Your "assignment dereference" won't work in Python 3.

from fuckitpy.

@asmeurer What do you mean by "assignment dereference"? I only found this in the original source:

source <- True # Dereference assignment to fix truthiness

Could anyone explain what it means? This bit is syntactically equivalent to source < -True, and subsequently source < -1. Such a comparison in Python 3 will throw a TypeError exception saying str() and int() are unorderable. Because this statement is essentially doing nothing. I simply removed it.

from fuckitpy.

That's the one.

from fuckitpy.

fc7aced

from fuckitpy.

@asmeurer Right... But that still does not explain why it's there. What race condition, and how this would help to fix a race condition?

from fuckitpy.

The whole thing is clearly a joke, as evidenced by the comment. It's just a shame that it will have to be a removed.

from fuckitpy.

You could always dereference the pointer the C way source*=True

from fuckitpy.

Thanks for all the discussion! Python3 compatibility is finally added in 4dc8167.

As for the discussion on the dereference assignment: I wasn't able to reproduce the race condition it addresses in Python 3, so I made the assignment only on Python 2.

from fuckitpy.

Awesome. Will you do a release on PyPI?

from fuckitpy.

Done in b7e0ccd. Thanks for the reminder!

from fuckitpy.