[issue38021] pep425 tag for AIX is inadequate

Change by Brett Cannon : -- nosy: -brett.cannon ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue38021] pep425 tag for AIX is inadequate

Michael Felt added the comment: On 26/11/2019 20:10, Paul Moore wrote: > Paul Moore added the comment: > >> replacement platform_tag, not compatibility tag. > Ah, I see, sorry. In that case, this should be fine, it's purely a CPython > question. There's obviously a follow-on discussion about

[issue38021] pep425 tag for AIX is inadequate

Paul Moore added the comment: > replacement platform_tag, not compatibility tag. Ah, I see, sorry. In that case, this should be fine, it's purely a CPython question. There's obviously a follow-on discussion about how that platform tag is *incorporated* into the compatibility tags, but as

[issue38021] pep425 tag for AIX is inadequate

Michael Felt added the comment: On 22/11/2019 10:42, Paul Moore wrote: > Paul Moore added the comment: > > PyPA member here - if this PR is defining new compatibility tags, replacement platform_tag, not compatibility tag. > I would have expected it to need discussion as a revision to PEP

[issue38021] pep425 tag for AIX is inadequate

Paul Moore added the comment: Thanks for the clarification, Nick. Yes, I agree that the basic "this is the tag that matches this precise CPython installation" is not the difficult part of the problem here, and if that is all that this issue is targeting, there should be no major problem.

[issue38021] pep425 tag for AIX is inadequate

Nick Coghlan added the comment: For folks that aren't aware, Michael and I have been discussing the AIX package tagging problem via email since his initial distutils-sig posts about it. It's genuinely murky as fixing the AIX problem doesn't *technically* require any PEP 425 changes, as the

[issue38021] pep425 tag for AIX is inadequate

Paul Moore added the comment: What complicates the issue for AIX (and reminds me very strongly of the MacOS and manylinux situations, both of which were defined after the original tag PEP, and so contain additional insights) is the business of certain tags being compatible across multiple

[issue38021] pep425 tag for AIX is inadequate

Michael Felt added the comment: @paul.moore - thanks for the comment. I am trying to work from both https://packaging.python.org/specifications/platform-compatibility-tags/ which describes in a few words the goals of PEP425. As to the PEP425 itself, it does not specify what a tag looks

[issue38021] pep425 tag for AIX is inadequate

Paul Moore added the comment: PyPA member here - if this PR is defining new compatibility tags, I would have expected it to need discussion as a revision to PEP 425, much like the manylinux efforts did. (It may actually be a closer parallel with MacOS, which didn't have a tagging PEP - I'm

[issue38021] pep425 tag for AIX is inadequate

Michael Felt added the comment: a) - thanks Ned, for the kind words. b) - the proposed (change to the tag) is "AIX.VRTL.YYWW.SZ". "AIX" - in caps, to distinguish from current tag starting as "aix" VRTL - 4 digit number, one digit for Version, one digit as Revision, and two digits for

[issue38021] pep425 tag for AIX is inadequate

Ned Deily added the comment: Brett, sorry I wasn't more explicit about my concerns here. I added you and Nick to this issue and to its PR not primarily to do do code review but because I think it brings up issues that I believe haven't been dealt with before in our evolving environment and

[issue38021] pep425 tag for AIX is inadequate

Brett Cannon added the comment: I'm not in a good position to review distutils stuff. -- ___ Python tracker ___ ___

[issue38021] pep425 tag for AIX is inadequate

Ned Deily added the comment: PEP 425 tags are now in the Python Packaging Authority realm. People from there should also be reviewing this issue and the new PR. CC-ing Brett and Nick for guidance. Also, assuming the feature is approved, I don't think it would be appropriate to backport

[issue38021] pep425 tag for AIX is inadequate

Change by Michael Felt : -- pull_requests: +16795 pull_request: https://github.com/python/cpython/pull/17303 ___ Python tracker ___

[issue38021] pep425 tag for AIX is inadequate

Michael Felt added the comment: When testing the PR with --with-pydebug I started getting the following error: root@x066:[/data/prj/python/git/pr-test]./python '-X' 'tracemalloc' -m test test_venv Run tests sequentially 0:00:00 [1/1] test_venv test test_venv failed -- Traceback (most recent

[issue38021] pep425 tag for AIX is inadequate

Change by Michael Felt : -- keywords: +patch pull_requests: +15337 stage: -> patch review pull_request: https://github.com/python/cpython/pull/15678 ___ Python tracker ___

[issue38021] pep425 tag for AIX is inadequate

Michael Felt added the comment: Thank you Ned. Not a justification perhaps, but a way to specify that it is support. Three+ years ago when I first worked on something for Lib/ctypes to get find_library() et al working for AIX I was also asked to add it as _aix.py similar to the macos

[issue38021] pep425 tag for AIX is inadequate

Ned Deily added the comment: I don't have an opinion about the bulk of the proposed change. But, since _osx_support was mentioned as a model for an _aix_support, I wanted to comment on the history of _osx_support. _osx_support was created as a separate module back when the distutils2 (aka

[issue38021] pep425 tag for AIX is inadequate

New submission from Michael Felt : PEP425 stats the platform tag is what distutils.util.get_platform() (and sysconfig.get_platform()) returns. By that definition - anything is okay, as long as something is returned. However, in practice, it is insufficient. Simplest case - there is no