From sh at changeset.nyc  Thu Oct  1 06:29:56 2020
From: sh at changeset.nyc (Sumana Harihareswara)
Date: Thu, 1 Oct 2020 06:29:56 -0400
Subject: [Wheel-builders] Pip users: big change coming this month
In-Reply-To: <3dc20496-47de-436f-9328-4699bfcdeaca@changeset.nyc>
References: <3dc20496-47de-436f-9328-4699bfcdeaca@changeset.nyc>
Message-ID: <28686f1c-eeef-8026-aa99-68d13c4007be@changeset.nyc>

Changes are coming to pip, Python's package installation tool, in 
October 2020. Please read and share this migration guide: 
https://pip.pypa.io/en/latest/user_guide/#changes-to-the-pip-dependency-resolver-in-20-2-2020 
.

We're working on improving the Python packaging toolchain, foundational 
work that will (in the long run) make the whole Python package 
installation experience way less confusing.

The pip team made a 2-minute video to explain what's up:

https://youtu.be/B4GQCBBsuNU

We are also doing user experience studies, and want you to sign up if 
you ever do anything with Python (whatever your level of 
skill/experience): 
http://www.ei8fdb.org/thoughts/2020/03/pip-ux-study-recruitment/

https://mastodon.social/@brainwane/104950044427849411 is a good toot to 
boost, and https://twitter.com/ThePSF/status/1311038036013199363 is a 
good tweet to retweet, if you want to help us get the word out.

MORE DETAILS: at the migration guide at 
https://pip.pypa.io/en/latest/user_guide/#changes-to-the-pip-dependency-resolver-in-20-2-2020 
.

On 7/30/20 10:58 AM, Sumana Harihareswara wrote:
> On behalf of the Python Packaging Authority, I am pleased to announce 
> that we have just released pip 20.2, a new version of pip. You can 
> install it by running python -m pip install --upgrade pip.

-- 
Sumana Harihareswara
Changeset Consulting
https://changeset.nyc

From adrien at guinet.me  Sun Oct 11 08:06:25 2020
From: adrien at guinet.me (Adrien Guinet)
Date: Sun, 11 Oct 2020 14:06:25 +0200
Subject: [Wheel-builders] Manylinux/non-intel dockers with a native x64
 compiler
Message-ID: <84314a68-c1b5-a932-1f72-4dc3afb0de2a@guinet.me>

Hello everyone,

I recently made a quick'n'dirty manylinux/aarch64-based docker that
contains an x64 version of clang (that targets aarch64). The idea was to
use it within github action to compile an aarch64 version of LLVM while
keeping a reasonable compile time.

The docker sources are here:
https://github.com/aguinet/manylinux2014_aarch64_cross_x64

It's used in dragonffi here (in order to build manylinux/aarch64
wheels):
https://github.com/aguinet/dragonffi/blob/master/.github/workflows/dist_publish.yml#L80

My question would be whether such manylinux2014_XX_cross_x64 dockers
would be of interest to other persons, and if it would make sens to move
this to more official manylinux repositories. I can dedicate some time
to make this happen in such a case.

Thanks for the work on all these manylinux dockers btw.

Regards,

Adrien.