From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: [BUG] Latest python38 package (3.8.7-1) fails to execute 'ensurepip', 3.8.3.-1 works
Date: Sat, 23 Jan 2021 19:47:16 +0100 [thread overview]
Message-ID: <d2adf631-a251-bb88-a015-0ab03d120835@gmail.com> (raw)
In-Reply-To: <BYAPR15MB26623A91DF4050112209FEA3BFBF9@BYAPR15MB2662.namprd15.prod.outlook.com>
On 23.01.2021 19:23, Oleh Svirshchevsky via Cygwin wrote:
> Latest python38 package (3.8.7-1) fails to execute 'ensurepip', 3.8.3.-1 works
>
> Latest version:
> $ python3.8.exe --version
> Python 3.8.7
> $ python3.8.exe -Im ensurepip --upgrade --default-pip
> Traceback (most recent call last):
> File "/usr/lib/python3.8/runpy.py", line 185, in _run_module_as_main
> mod_name, mod_spec, code = _get_module_details(mod_name, _Error)
> File "/usr/lib/python3.8/runpy.py", line 144, in _get_module_details
> return _get_module_details(pkg_main_name, error)
> File "/usr/lib/python3.8/runpy.py", line 111, in _get_module_details
> __import__(pkg_name)
> File "/usr/lib/python3.8/ensurepip/__init__.py", line 121
> with open(os.path.join(_WHEEL_DIR, wheel_name), "rb") as sfp:
> ^
> IndentationError: unexpected indent
>
>
> Older version:
> $ python3.8.exe --version
> Python 3.8.3
> $ python3.8.exe -Im ensurepip --upgrade --default-pip
> Looking in links: /tmp/tmpxxpxh_dl
> Requirement already up-to-date: setuptools in /usr/lib/python3.8/site-packages (51.1.1)
> Requirement already up-to-date: pip in /usr/lib/python3.8/site-packages (20.3.3)
thanks for the report.
I will look on the root cause
Marco
next prev parent reply other threads:[~2021-01-23 18:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-23 18:23 Oleh Svirshchevsky
2021-01-23 18:47 ` Marco Atzeri [this message]
2021-01-23 19:13 ` Marco Atzeri
2021-01-24 6:58 ` Oleh Svirshchevsky
2021-01-24 8:27 ` Marco Atzeri
2021-01-30 15:00 ` Marco Atzeri
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=d2adf631-a251-bb88-a015-0ab03d120835@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin@cygwin.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).