** Also affects: python-netaddr (Ubuntu)
Importance: Undecided
Status: New
** Changed in: python-netaddr (Ubuntu Focal)
Status: New => In Progress
** Changed in: python-netaddr (Ubuntu Focal)
Assignee: (unassigned) => Eric Desrochers (slashd)
** Changed in: python-netaddr
I have just re-test in a focal lxd container, the installation worked.
ii python3-jmespath 0.9.4-2
all JSON Matching Expressions (Python 3)
but could mislead the user that it wasn't successfully installed:
Setting up python3-jmespath (0.9.4-2) ...
One of the impact is:
https://github.com/jmespath/jmespath.py/issues/201
** Bug watch added: github.com/jmespath/jmespath.py/issues #201
https://github.com/jmespath/jmespath.py/issues/201
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
While reviewing this SRU I'm trying to measure the severity of the
current situation. Since this seems to be a warning, does it actually
impact users in any way besides printing the warning? Are there any
consequences of it? Are any of the reverse-dependencies impacted,
requiring this fix?
--
Focal debdiff
** Patch added: "Focal debdiff"
https://bugs.launchpad.net/ubuntu/+source/python-jmespath/+bug/1877792/+attachment/5531626/+files/f.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Bionic debdiff
** Patch added: "Bionic debdiff"
https://bugs.launchpad.net/ubuntu/+source/python-jmespath/+bug/1877792/+attachment/5531623/+files/b.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: python-jmespath (Ubuntu Focal)
Status: Confirmed => In Progress
** Changed in: python-jmespath (Ubuntu Focal)
Assignee: (unassigned) => Eric Desrochers (slashd)
** Changed in: python-jmespath (Ubuntu Bionic)
Status: Confirmed => In Progress
** Changed in:
** Description changed:
[IMPACT]
* Allow broader Ops/Eng team to consume Ansible from our packages
instead of the upstream PyPi repositories in order to fix this warning.
* Sanitize package installation:
Setting up python3-jmespath (0.9.4-2) ...
** Description changed:
[IMPACT]
* Allow broader Ops/Eng team to consume Ansible from our packages
instead of the upstream PyPi repositories in order to fix this warning.
* Sanitize package installation:
Setting up python3-jmespath (0.9.4-2) ...
** Description changed:
[IMPACT]
* Allow broader Ops/Eng team to consume Ansible from our packages
instead of the upstream PyPi repositories in order to fix this warning.
* Sanitize package installation:
Setting up python3-jmespath (0.9.4-2) ...
** Description changed:
[IMPACT]
* Allow broader Ops/Eng team to consume Ansible from our packages
instead of the upstream PyPi repositories in order to fix this warning.
* Sanitize package installation:
Setting up python3-jmespath (0.9.4-2) ...
** Description changed:
+ [IMPACT]
+
+ [TEST CASE]
+
+ ** Scenario #1 **
+ This could be reproduced outside python-jmespath as follows (a little script
I have written to compare result between py2 and py3 :
+
+ # reproducer_test.py
+
+ def reproducer(x,y):
+ if x is 0 or x is 1:
+
** Also affects: ansible (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: python-jmespath (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: ansible (Ubuntu Impish)
Importance: Undecided
Status: Invalid
** Also affects:
Version information for python-jmespath in the Ubuntu 20.04 LXC Linux
container:
root@afns1:/# dpkg -l | grep jmespath
ii python3-jmespath 0.9.4-2 all
JSON Matching Expressions (Python 3)
--
You received this bug notification because you are a
Hi, I am also seeing this error when running the following install in a
Ubuntu 20.04 focal fossa on amd64 running in an LXC Linux Container:
The command run is:
COMMAND=/bin/lxc-attach -n nsa -- sudo apt-get -y install bind9 isc-
dhcp-server bind9utils dnsutils openssh-server man awscli sshpass
** Changed in: python-jmespath (Debian)
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877792
Title:
jmespath SyntaxWarning: "is" with a literal.
To manage
python-jmespath (0.9.5-1) unstable; urgency=medium
[ TANIGUCHI Takaki ]
* add CI config
* New upstream version 0.9.5
- Fix SyntaxWarning (Closes: #953534)
* Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
Repository-Browse.
* Update standards version to
It looks like https://launchpad.net/ubuntu/+source/python-
jmespath/0.9.5-1 addresses this issue, from Groovy and Sid.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877792
Title:
jmespath
I confirm this. Running any Ansible playbook displays the following
warning on every task which is quite annoying:
/usr/lib/python3/dist-packages/jmespath/visitor.py:32: SyntaxWarning: "is" with
a literal. Did you mean "=="?
if x is 0 or x is 1:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: python-jmespath (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877792
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ansible (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877792
Title:
21 matches
Mail list logo
