#33778: pyproject.toml uses the incorrect "legacy" setuptools backend and
unnecessary wheel dep
------------------------------+------------------------------------
     Reporter:  Michał Górny  |                    Owner:  nobody
         Type:  Bug           |                   Status:  new
    Component:  Packaging     |                  Version:  4.0
     Severity:  Normal        |               Resolution:
     Keywords:                |             Triage Stage:  Accepted
    Has patch:  0             |      Needs documentation:  0
  Needs tests:  0             |  Patch needs improvement:  0
Easy pickings:  1             |                    UI/UX:  0
------------------------------+------------------------------------

Comment (by Rui):

 Replying to [ticket:33778 Michał Górny]:
 hello,I'm new to package program, what means to used incorrect legacy
 backend?how to fix it? Besides,just need to remove duplicated 'wheel'
 requires?
 > The pyproject.toml file lists the following:
 >
 > {{{
 > [build-system]
 > requires = ['setuptools>=40.8.0', 'wheel']
 > build-backend = 'setuptools.build_meta:__legacy__'
 > }}}
 >
 > The wheel dependency is redundant and discouraged here. Setuptools adds
 this dependency via the backend automatically since day one. It was
 historically included in the documentation but it was a mistake. See:
 
https://github.com/pypa/setuptools/commit/f7d30a9529378cf69054b5176249e5457aaf640a
 >
 > The legacy backend was never supposed to be used in pyproject.toml. It
 is only an "internal" fallback that is used by tools like pip when
 pyproject.toml is not present at all. The regular backend must always be
 used in pyproject.toml. See:
 https://github.com/pypa/setuptools/issues/1689

-- 
Ticket URL: <https://code.djangoproject.com/ticket/33778#comment:7>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/01070181a6559774-e991ea31-38bb-480f-9b45-f6e238cedc37-000000%40eu-central-1.amazonses.com.

Reply via email to