From: sgn <sgn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] [BUG] python byte-compilation syntax error `"is" with a literal. Did you mean "=="?`
Date: Wed, 19 Aug 2020 18:14:03 +0200 [thread overview]
Message-ID: <20200819161403.WtYsfVaovSBMvCK5KnVhXAZjBJxqd1vp-5iz-e9HMXE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24239@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1149 bytes --]
Closed issue by zenny on void-packages repository
https://github.com/void-linux/void-packages/issues/24239
Description:
Hi,
I just tried to `vpm upgrade` and got the following syntax error:
```
"is" with a literal. Did you mean "=="?
```
Details:
```
...
python3-3.8.5_1: configuring ...
Byte-compiling python code in usr/lib/python3.8...
usr/lib/python3.8/site-packages/enchant/checker/CmdLineChecker.py:163: SyntaxWarning:
"is" with a literal. Did you mean "=="?
if index is 0:
usr/lib/python3.8/site-packages/tzlocal/unix.py:141: SyntaxWarning: "is not" with a literal. Did you mean "!="?
while start is not 0:
usr/lib/python3.8/site-packages/enchant/checker/CmdLineChecker.py:163: SyntaxWarning:
"is" with a literal. Did you mean "=="?
if index is 0:
usr/lib/python3.8/site-packages/tzlocal/unix.py:141: SyntaxWarning: "is not" with a literal. Did you mean "!="?
while start is not 0:
Byte-compiling python3.8 code for module README.txt...
Updating ldconfig(8) cache...
python3-3.8.5_1: updated successfully.
python3-devel-3.8.5_1: configuring ...
python3-devel-3.8.5_1: updated successfully.
...
```
prev parent reply other threads:[~2020-08-19 16:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-12 5:01 [ISSUE] " zenny
2020-08-12 11:50 ` sgn
2020-08-12 12:20 ` ericonr
2020-08-13 15:36 ` sgn
2020-08-13 15:36 ` [ISSUE] [CLOSED] " sgn
2020-08-13 15:37 ` sgn
2020-08-19 16:14 ` sgn
2020-08-19 16:14 ` sgn [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200819161403.WtYsfVaovSBMvCK5KnVhXAZjBJxqd1vp-5iz-e9HMXE@z \
--to=sgn@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).