-
-
Notifications
You must be signed in to change notification settings - Fork 15.5k
pgcli: 2.0.0 -> 2.0.1 #51269
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
pgcli: 2.0.0 -> 2.0.1 #51269
Conversation
Changelog: https://github.com/dbcli/pgcli/blob/master/changelog.rst#201 Major feature of note is Python 3.7 support.
Failure on x86_64-darwin (full log) Attempted: pgcli Partial log (click to expand)
|
Failure on x86_64-linux (full log) Attempted: pgcli Partial log (click to expand)
|
Failure on aarch64-linux (full log) Attempted: pgcli Partial log (click to expand)
|
@aneeshusa Build fails with:
|
@worldofpeace looks like there was an issue due to nixpkgs still being python2 by default, I have python3 by default and had no issues. Pushed a commit to pin to Python 3 which I've tested locally. |
But this leaves the python 2 build broken. If I'm understanding this correctly, applications for both interpreter versions want to migrate to prompt_toolkit v2+. Yet some had no plans to. It seems things were correct and allowed migration until f0b49c4#diff-2afbba83e1b14f9e0c304c769831a0e2 hit. @FRidh I feel like that should be reverted. |
On Python 2 nixpkgs uses the older prompt_toolkit 1.x line instead of the latest 2.x line. The 1.x line is no longer developed and isn't listed as supporting Python 3.6 or above. Since this is an application, always use Python 3.
a129f53
to
cb261c4
Compare
Since this is an application and not a library, I think it's fine to not have a Python 2 build. Personally, I'm also not interested in spending time on Python 2 support since it's 2018. Agreed that f0b49c4 seems strange and I'd want to revert it, but maybe there was a good reason for it. |
I get this traceback when trying to execute on NixOS: Click to expand
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree with having pgcli in Python 3 only. It works here...
@worldofpeace could you write how you run the command so that we could reproduce the traceback? |
I simply executed it with no arguments. |
|
Merged in 3dbbd9f |
Motivation for this change
Changelog: https://github.com/dbcli/pgcli/blob/master/changelog.rst#201
Major feature of note is Python 3.7 support.
Things done
sandbox
innix.conf
on non-NixOS)nix-shell -p nox --run "nox-review wip"
./result/bin/
)nix path-info -S
before and after)