-
-
Notifications
You must be signed in to change notification settings - Fork 14.6k
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
python3Packages.yowsup: 2.5.2 -> 2.5.7 #39926
Conversation
@@ -5,7 +5,7 @@ | |||
buildPythonPackage rec { | |||
name = "${pname}-${version}"; |
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.
drop this line
Even if yowsup pins |
the following comment contains several resources that explain the issue: tgalal/yowsup#2416 (comment) Unfortunately the combination of |
pname = "yowsup"; | ||
version = "2.5.2"; | ||
version = "2.5.7"; | ||
|
||
# python2 is currently incompatible with yowsup: | ||
# https://github.com/tgalal/yowsup/issues/2325#issuecomment-343516519 |
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.
Could you please update this message so it mentions the six==1.11 incompatibility?
The latest update of `yowsup` (https://github.com/tgalal/yowsup/releases/tag/v2.5.7) contains the following fixes: * Updated tokens * Fixed tgalal/yowsup#1842: Bug in protocol_groups RemoveGroupsNotificationProtocolEntity * Other minor bug fixes The `argparse-dependency.patch` required a rebase onto the latest version of `setup.py` and ensures that `argparse` won't be needed as extra dependency as our `python3` package ships `argparse` by default. A short note to Python 2 support: the actual issue related to Python 2.x support has been resolved (tgalal/yowsup#2325 (comment)), however this relies on `six==1.10` which isn't support by `nixpkgs` as `six` has been bumped to `1.11`. When trying to inject a patched version of our `six` package based on `six==1.10` you'll run into issues with duplicated libraries in your closure as further build dependencies (`pytest` in this case) use the latest `six` version. As Python 2.7 will die in 2020 (https://pythonclock.org/) and patching around in the dependencies of `pytest` to get `yowsup` running isn't worth the effort in my opinion I decided to keep the Python 2.x build disabled for now.
@dotlambda done :-) |
ping @dotlambda |
@GrahamcOfBorg build python2.pkgs.yowsup python3.pkgs.yowsup |
Success on x86_64-linux (full log) Attempted: python3.pkgs.yowsup The following builds were skipped because they don't evaluate on x86_64-linux: python2.pkgs.yowsup Partial log (click to expand)
|
Success on aarch64-linux (full log) Attempted: python3.pkgs.yowsup The following builds were skipped because they don't evaluate on aarch64-linux: python2.pkgs.yowsup Partial log (click to expand)
|
Motivation for this change
The latest update of
yowsup
(https://github.com/tgalal/yowsup/releases/tag/v2.5.7)contains the following fixes:
The
argparse-dependency.patch
required a rebase onto the latestversion of
setup.py
and ensures thatargparse
won't be needed asextra dependency as our
python3
package shipsargparse
by default.A short note to Python 2 support:
the actual issue related to Python 2.x support has been resolved
(tgalal/yowsup#2325 (comment)),
however this relies on
six==1.10
which isn't support bynixpkgs
assix
has been bumped to1.11
. When trying to inject a patched versionof our
six
package based onsix==1.10
you'll run into issues withduplicated libraries in your closure as further build dependencies
(
pytest
in this case) use the latestsix
version. As Python 2.7 willdie in 2020 (https://pythonclock.org/) and patching around in the
dependencies of
pytest
to getyowsup
running isn't worth the effortin my opinion I decided to keep the Python 2.x build disabled for now.
Things done
build-use-sandbox
innix.conf
on non-NixOS)nix-shell -p nox --run "nox-review wip"
./result/bin/
)