New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
updated Pg8000 #762
updated Pg8000 #762
Conversation
sys.path is getting weird..... |
I see but it's the only way I found so far |
let's rethink a bit in web2py-developers. |
I tried a bit more by removing all references of pg8000 in all imports and eventually the import worked. |
Ok.. so maybe we can accept the sys.path as a temporary workaround waiting for better solutions. |
the point now is : why web2py should work around something that is so buggy ? let's wait for a proper fix and live without tampering web2py internals. |
Hey all. If I'm understanding the discussion here, it seems like you're having troubles incorporating pg8000 into this codebase because of the use of absolute imports in the code? It would definitely make sense to change pg8000 to use relative imports for it's cross-module references, and I'd happily accept a PR to fix that issue. If a PR isn't forthcoming, I'd fix it myself, but I can't do that immediately. The only concern I have is that pg8000 supports older versions of Python back to 2.5, but I believe that's when relative imports were first added to Python so it shouldn't be a problem. |
@niphlod, @gi0baro I understand your points. I see two options:
|
@ilvalle I agree for no. 2 |
@ilvalle since mfenniak/pg8000#71 is merged, you can update pg8000 to latest code revision and remove the |
Ok, I've updated pg8000 to the last version and rebase the last commit of this PR. |
Thank you all for the hard work! |
this somehow got merged wrongly (came from #762)
No description provided.