[issue28027] Remove Lib/plat-*/* files

STINNER Victor added the comment: Thank you Zachary for this removal ;-) -- ___ Python tracker ___

[issue28027] Remove Lib/plat-*/* files

Zachary Ware added the comment: Since we've reached 3.6.3 with no complaints that have made it to me, I'm going to go ahead and close the issue. -- resolution: -> fixed status: open -> closed ___ Python tracker

[issue28027] Remove Lib/plat-*/* files

Guido van Rossum added the comment: The modules should remain deleted for 3.6b1 so we can see if there are actually any complaints -- if we get any we can consider restoring them for b2. I fail to be convinced by the arguments against deletion brought up so far -- the "evidence" produced is way

[issue28027] Remove Lib/plat-*/* files

STINNER Victor added the comment: Sorry, I'm leaving this discussion now. -- ___ Python tracker ___ ___

[issue28027] Remove Lib/plat-*/* files

Zachary Ware added the comment: "Agreed" is a bit strong, I still don't agree that the change was bad or should be reverted. I'm just not ruling out the possibility of a partial (because there is absolutely no reason to re-add the files for any platform but Linux and *maybe* OSX) reversion

[issue28027] Remove Lib/plat-*/* files

Matthias Klose added the comment: "It's a matter of maintenance burden". No I don't think so. As agreed on IRC with zware, I'll restore the removed modules, including a deprecation notice. -- assignee: zach.ware -> doko resolution: fixed -> status: closed -> open

[issue28027] Remove Lib/plat-*/* files

STINNER Victor added the comment: Matthias Klose: Maybe you didn't understand something: breaking the backward compatibility was a deliberate choice. It's a matter of maintenance burden versus the number of broken applications. According to your search, there are only 8 projects in the wild

[issue28027] Remove Lib/plat-*/* files

Matthias Klose added the comment: you asked for evidence, you got evidence. re-opening the issue again. feel free to close it again without any evidence, and stating that you ignore the usual deprecation rules. -- resolution: fixed -> status: closed -> open

[issue28027] Remove Lib/plat-*/* files

Zachary Ware added the comment: With no solid evidence against the change and much joy with the change, I'm reclosing the issue. doko, if people complain to you about being broken by this, feel free to refer them to me. -- resolution: -> fixed status: open -> closed

[issue28027] Remove Lib/plat-*/* files

STINNER Victor added the comment: The FreeBSD packager told me that he is *very* happy to see these modules go away, it was also a pain for him to maintain a patch for them. The maintaince burden is even wider than Python source code. -- ___ Python

[issue28027] Remove Lib/plat-*/* files

Xavier de Gaye added the comment: > Since the 3.6 cycle, these modules are regenerated for the build, so they are > not outdated anymore. They are not a maintenance burden either. Indeed, they are regenerated by the changes made in issue 23968 ("rename the platform directory from

[issue28027] Remove Lib/plat-*/* files

Zachary Ware added the comment: Because in every release of Python they have been undocumented, in any recent release of Python they have been inaccurate (at best) and probably unnecessary, they have been unmaintained for years, the presence of the plat-* dir on sys.path slows down imports

[issue28027] Remove Lib/plat-*/* files

Changes by Xavier de Gaye : -- nosy: +xdegaye ___ Python tracker ___ ___ Python-bugs-list

[issue28027] Remove Lib/plat-*/* files

Matthias Klose added the comment: these projects are the ones packaged by Debian; there are surely others. Now again, why can't the actual removal for 3.7, following the usual deprecation rules? -- ___ Python tracker

[issue28027] Remove Lib/plat-*/* files

STINNER Victor added the comment: > https://codesearch.debian.net/search?q=import+DLFCN I see 8 projects: boost, trilinos, vtk6, openbabel, gdcm, paraview, ecasound, yade. It doesn't like a giant project to update them. > boost1.58_1.58.0+dfsg-5.1/libs/mpi/build/__init__.py > > import sys >

[issue28027] Remove Lib/plat-*/* files

Zachary Ware added the comment: Those boost imports will never be triggered in Python 3, because sys.platform will never be 'linux2'. -- ___ Python tracker

[issue28027] Remove Lib/plat-*/* files

Matthias Klose added the comment: whatever you searched, there are regressions: https://codesearch.debian.net/search?q=import+DLFCN some of these have conditional imports, however even boost uses unconditional imports, and is often used as an embedded copy. --

[issue28027] Remove Lib/plat-*/* files

Zachary Ware added the comment: I have been searching sources.debian.net, and have found no evidence of anything that would be broken by this. Every use of these modules that I have found has been already wrapped in try/except ImportError, or is in code that is fairly obviously not meant for

[issue28027] Remove Lib/plat-*/* files

Guido van Rossum added the comment: No, you need to demonstrate that they are used (despite undocumented). On Fri, Sep 9, 2016 at 2:26 PM, Matthias Klose wrote: > > Matthias Klose added the comment: > > Since the 3.6 cycle, these modules are regenerated for the build,

[issue28027] Remove Lib/plat-*/* files

Matthias Klose added the comment: Since the 3.6 cycle, these modules are regenerated for the build, so they are not outdated anymore. They are not a maintenance burden either. So I'd like to see these available in 3.6, and documented as deprecated. Then removed in 3.7. Apparently the

[issue28027] Remove Lib/plat-*/* files

Guido van Rossum added the comment: Why? Do you have a dependency on these? None of them are documented. Do you propose to document them just so we can mark them deprecated? -- ___ Python tracker

[issue28027] Remove Lib/plat-*/* files

Matthias Klose added the comment: the removal of these modules should follow the normal deprecation process, for 3.6, then be removed for 3.7. There is no harm for this approach. -- nosy: +doko resolution: fixed -> status: closed -> open ___

[issue28027] Remove Lib/plat-*/* files

STINNER Victor added the comment: FYI I first proposed to remove plat-* in 2011: https://mail.python.org/pipermail/python-dev/2011-October/114105.html That's why I added os.RTDL_* constants: https://docs.python.org/dev/library/os.html#os.RTLD_LAZY --

[issue28027] Remove Lib/plat-*/* files

koobs added the comment: YES, finally. Thanks :) -- nosy: +koobs ___ Python tracker ___ ___ Python-bugs-list

[issue28027] Remove Lib/plat-*/* files

STINNER Victor added the comment: Yeah! Thanks Zach :-) -- ___ Python tracker ___ ___ Python-bugs-list

[issue28027] Remove Lib/plat-*/* files

Zachary Ware added the comment: None of the buildbots have complained about this (they've been too busy complaining about other things), so I'm closing it. -- resolution: -> fixed stage: -> resolved status: open -> closed ___ Python tracker

[issue28027] Remove Lib/plat-*/* files

STINNER Victor added the comment: > Issue #28027: Mention the names of the removed modules in Misc/NEWS Thanks :-) -- ___ Python tracker ___

[issue28027] Remove Lib/plat-*/* files

Roundup Robot added the comment: New changeset e256583e6062 by Zachary Ware in branch 'default': Issue #28027: Mention the names of the removed modules in Misc/NEWS https://hg.python.org/cpython/rev/e256583e6062 -- ___ Python tracker

[issue28027] Remove Lib/plat-*/* files

Zachary Ware added the comment: Will close this after the buildbots have confirmed they don't hate it. -- ___ Python tracker ___

[issue28027] Remove Lib/plat-*/* files

Roundup Robot added the comment: New changeset 14d89359a389 by Zachary Ware in branch 'default': Issue #28027: Remove Lib/plat-* files https://hg.python.org/cpython/rev/14d89359a389 -- nosy: +python-dev ___ Python tracker

[issue28027] Remove Lib/plat-*/* files

New submission from Zachary Ware: After discussion at the core dev sprints, Guido has decreed that the files in Lib/plat-* can and should be removed. -- assignee: zach.ware messages: 275106 nosy: gvanrossum, haypo, ned.deily, zach.ware priority: normal severity: normal status: open