Re: Approaching wheel 1.0

Nick Coghlan <[email protected]>
Newsgroups gmane.comp.python.distutils.devel
Message-ID <CADiSq7fP2gaztxOpUSofT0DVW5xwuLZbqOucFdure2XzXdj51A@mail.gmail.com>
On 17 July 2018 at 23:44,  <[email protected]> wrote:
> Today I pushed 29 new commits to the pypa/wheel repository, closing around
> 15 issues. This is a major overhaul/refactoring of the wheel project. Here's
> the short list of major changes:
>
> * The documentation has been rewritten to conform to PyPA guidelines
> (https://gist.github.com/qwcode/8431828)
> * Wheel signing and verifying features were stripped out, as they were
> scarcely used and would have potentially presented a significant maintenance
> burden
> * The wheel install feature was also stripped out, largely from the same
> reason as above
> * Added a new command, "wheel pack" that will create a new wheel file from a
> previously unpacked wheel directory, regenerating the RECORD file in the
> process
> * Added a new metadata key, "license_files" which can be used to include
> multiple license files in wheels (this deprecates the "license_file" key)

Very cool!

> There are still a few issues to work out before I'm comfortable releasing
> 1.0.0 final. For that, I would like to enlist the help of the Python
> packaging community, as I may not have the necessary expertise:
>
> * Py_UNICODE_SIZE / WITH_PYMALLOC / Py_DEBUG on Windows:
> https://github.com/pypa/wheel/issues/171
> * Supporting tools like milksnake by allowing platform specific wheel tags
> with ABI set to "none":
> * https://github.com/pypa/wheel/issues/125
> * https://github.com/pypa/wheel/issues/153
> * https://github.com/pypa/wheel/issues/175
> * https://github.com/pypa/wheel/issues/185
> * Automatically detecting C extensions that use the limited ABI and tagging
> wheels without an explicit --py-limited-abi:
> https://github.com/pypa/wheel/issues/198
> * bdist_wheel not cleaning build directory (really a distutils problem, but
> can wheel reasonably do something here?)
> https://github.com/pypa/wheel/issues/117
>
> I mostly need help defining the concrete steps to take to resolve these
> issues.

I've commented where I could, but that was basically just the ones
where you seemed to be pondering possible command line UX options -
for the ones related to the actual extension module build process, I
believe you already know significantly more than I do :(

Cheers,
Nick.

-- 
Nick Coghlan   |   [email protected]   |   Brisbane, Australia
--
Distutils-SIG mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mm3/mailman3/lists/distutils-sig.python.org/
Message archived at https://mail.python.org/mm3/archives/list/[email protected]/message/NYT5TG3AVWPZMN3SB2IGBXPNRYYVS3CV/
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.