Skip to content

Closes #667: advise against using distutils directly#672

Closed
ncoghlan wants to merge 3 commits intopypa:mainfrom
ncoghlan:issue-667-note-problem-with-old-distutils-core-examples
Closed

Closes #667: advise against using distutils directly#672
ncoghlan wants to merge 3 commits intopypa:mainfrom
ncoghlan:issue-667-note-problem-with-old-distutils-core-examples

Conversation

@ncoghlan
Copy link
Copy Markdown
Member

No description provided.

@ncoghlan ncoghlan requested review from di and pfmoore November 10, 2019 04:39
@ncoghlan
Copy link
Copy Markdown
Member Author

Arising from both the discussion in #667 (and the linked psutil issue), as well as pypa/packaging-problems#288 (where bdist_wheel was failing for a user because their setup.py was still importing from distutils.core)

``setuptools``. This is a `legacy approach`_ that installers [1]_ support
for backwards compatibility purposes, but using the legacy ``distutils`` API
directly in new projects is strongly discouraged, as it means that newer
build commands, like ``setup.py bdist_wheel``, won't work.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd like to see this worded a little more strongly, to address 2 points:

  1. The "backward compatibility" support is limited, and may not be compatible with newer installer features (like build isolation). It also won't be maintained indefinitely, which leads to....
  2. Existing projects are strongly advised to move away from using the legacy distutils API to ensure that they will continue working as installers evolve.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @ncoghlan, are you planning to address this?

Copy link
Copy Markdown
Member

@di di left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, agree w/ @pfmoore's comment.

Comment thread source/tutorials/packaging-projects.rst Outdated
Base automatically changed from master to main January 21, 2021 18:44
@webknjaz
Copy link
Copy Markdown
Member

Hey @ncoghlan, could you solve the merge conflict here?

Co-authored-by: Dustin Ingram <di@users.noreply.github.com>
@webknjaz
Copy link
Copy Markdown
Member

webknjaz commented Sep 2, 2021

@ncoghlan also, there's a huge merge conflict that needs to be solved manually (the browser-based UI is not very helpful here).

@astrojuanlu
Copy link
Copy Markdown
Contributor

I'd be happy to take over this and bring it to a mergeable state.

@webknjaz
Copy link
Copy Markdown
Member

webknjaz commented Dec 5, 2021

@astrojuanlu feel free to send a PR based on this.

@astrojuanlu
Copy link
Copy Markdown
Contributor

Done: #1028

@di di closed this in #1028 Dec 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants