Re: [MacPorts] #68984: dblatex @0.3.12_2 still needs Python 3.10 (was: dblatex @0.3.12₂ still needs Python 3.10)

[MacPorts]

#68984: dblatex @0.3.12_2 still needs Python 3.10
------------------------+------------------------
  Reporter:  ballapete  |      Owner:  neverpanic
      Type:  defect     |     Status:  assigned
  Priority:  Normal     |  Milestone:
 Component:  ports      |    Version:  2.8.1
Resolution:             |   Keywords:
      Port:  dblatex    |
------------------------+------------------------
Changes (by ryandesign):

 * status:  new => assigned
 * owner:  (none) => neverpanic


Comment:

 Simply changing 310 to 311 causes a warning:

 {{{
 /opt/local/var/macports/build/_Volumes_Shared_macports-
 ports_textproc_dblatex/dblatex/work/dblatex3-0.3.12/setup.py:255:
 SetuptoolsDeprecationWarning: setup.py install is deprecated.
 !!

 ********************************************************************************
         Please avoid running ``setup.py`` directly.
         Instead, use pypa/build, pypa/installer or other
         standards-based tools.

         See https://blog.ganssle.io/articles/2021/10/setup-py-
 deprecated.html for details.
 ********************************************************************************

 !!
 }}}

 Using 312 causes build failure:

 {{{
 Traceback (most recent call last):
   File "/opt/local/var/macports/build/_Volumes_Shared_macports-
 ports_textproc_dblatex/dblatex/work/dblatex3-0.3.12/setup.py", line 15, in
 <module>
     from setuptools import setup
 ImportError: cannot import name 'setup' from 'setuptools' (unknown
 location)

 During handling of the above exception, another exception occurred:

 Traceback (most recent call last):
   File "/opt/local/var/macports/build/_Volumes_Shared_macports-
 ports_textproc_dblatex/dblatex/work/dblatex3-0.3.12/setup.py", line 18, in
 <module>
     from distutils.core import setup
 ModuleNotFoundError: No module named 'distutils'
 }}}

 I guess for python312 we would need to use pep517 but dblatex is
 apparently incompatible with that; see
 [3593e1ca3bd419d0dd6d494dac11e24ab4cd7933/macports-ports]. I don't see any
 upstream bug report about that though.

-- 
Ticket URL: <https://trac.macports.org/ticket/68984#comment:1>
MacPorts <https://www.macports.org/>
Ports system for macOS