str<->bytes conversion not automatic with python version >=3.2 about fusepy HOT 4 OPEN

My patches on github.com: https://github.com/terencehonles/fusepy probably fix 
what you need (Ideally my patches will be pushed upstream)

Also, the Python 3 module (fuse3.py, and memory3.py example) is getting quite 
out of date -- many fixes have been made to fuse.py that have not been applied 
to fuse3. The long-term solution is to do what Terence is suggesting and have 
just one file that works on both 2 and 3. But his changes are quite drastic, 
and somewhat broken, so in the short term, I am providing two minimalistic 
patches that get this code working properly in Python 3.

First, python3-merge-to-r65.patch simply takes all of the changes to fuse.py 
and memory.py from SVN r37 to r65, and applies them to fuse3.py and memory3.py.

Then (once that first patch is applied), python3-unicode-fixes.patch fixes up 
the string encoding issues in fuse.py and memory.py so that it works in Python 
3.2. I have not forward-ported the other examples but I could do so.

Important note about str vs bytes: I have quite deliberately forced the user's 
code to deal with bytes objects. My patch will not work if users expect or 
produce str values -- you must deal with bytes values. I explained the 
reasoning for this on Issue 32 
(http://code.google.com/p/fusepy/issues/detail?id=32#c5) -- POSIX filenames are 
bytes, not Unicode strings (not specifically UTF-8) and therefore, when you 
write a Fuse module in Python 3, you must deal with bytes, not strs. Note that 
Terence's patch doesn't satisfy this requirement.

Sorry, I found some more places (in the default implementations of Operations 
methods) that needed to be turned into bytes literals. Attaching new patch.

Oh, I just noticed that the website states that development has moved to 
GitHub. I suppose this is the official branch now? If this is so, ignore my 
patches here. I'll file a new issue on GitHub.