Comment #8 on issue 275 by the.real...@gmail.com: Incorrect installation with setup.py breaks local override
http://code.google.com/p/protobuf/issues/detail?id=275
Well, setuptools handles the magic for you if you use it for the local installation. Conversely, if you use virtualenv, it'll similarly handle the magic for you. (I think it does, anyway.)
Pretty much, the process of managing namespace packages *is* magic right now, so you just have to choose which magician (setuptools, virtualenv, ...) is going to handle it for you, or else handle all the path munging yourself. (Which is even more unpleasant... and is why the tools exist.)
That's what PEP 382 is about, btw -- getting rid of the hackery that's currently needed for namespace packages to work, and replacing it with a builtin declarative mechanism, to replace all the old imperative "magic" tools.
Unfortunately, PEP 382 isn't implemented yet. Maybe you can get somebody at Google to work on it as a 20% project? ;-)
-- You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To post to this group, send email to protobuf@googlegroups.com. To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
