[MacPorts] #62682: py-dns-lexicon: do not check active variant of poetry port

[MacPorts]

#62682: py-dns-lexicon: do not check active variant of poetry port
-----------------------------+-------------------------
  Reporter:  ryandesign      |      Owner:  Schamschula
      Type:  defect          |     Status:  assigned
  Priority:  Normal          |  Milestone:
 Component:  ports           |    Version:  2.6.4
Resolution:                  |   Keywords:
      Port:  py-dns-lexicon  |
-----------------------------+-------------------------

Comment (by harens):

 I don't think py-dns-lexicon requires poetry as a build dependency in the
 first place, although please let me know if I've missed something here.
 Ever since [https://github.com/python-poetry/poetry/issues/1975 python-
 poetry/poetry#1975], assuming you're retrieving the files from PyPi, you
 can treat it as you would any other python package. This is since a
 standard `setup.py` is generated in the final product.

 As an example, [https://github.com/macports/macports-
 ports/blob/a6426e58f2566b7f2309140f6ec3123dce4da0d8/python/py-
 rich/Portfile py-rich] makes use of poetry, but it isn't actually required
 as a dependency (unless you use the GitHub PG, in which case things get
 tricky).

 The reason I made use of poetry in py-cipheycore is since I needed to use
 the CLT to generate a [https://docs.python.org/3/distutils/sourcedist.html
 source distribution]. At least in this scenario, it didn't matter which
 python variant of poetry was used since the CLT was the same either way
 and produced the correct file.

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