[Slackbuilds-users] important info regarding python3-hatchling update

[fourtysixandtwo]

On Tue, Sep 10, 2024 at 12:55 PM Jeremy Hansen <jebrhansen+SBo at gmail.com> wrote:
> export SETUPTOOLS_SCM_PRETEND_VERSION=$VERSION
>
> and a few
>
> export PDM_BUILD_SCM_VERSION=$VERSION
>
> to fix some issue with versions not being detected properly during build time (although, I believe several are due to me choosing GitHub tarballs instead of PyPi, which are packaged differently). If those hacks were to be fixed by these updates, I'd remove them.

I use the pypi tarballs solely because I can also grab the MD5SUM they
provide with my update script.  It is a bonus that I haven't had to
use those methods above with any builds I maintain.  I just checked
with python3-tox and python3-pyproject-api tarballs from pypi and they
both include a "src/*/*version.py".  One does have to watch for the
change in source from say pyproject-api to pyproject_api in both
download and SRCNAM though.

Have you come across this for troubleshooting?
export SETUPTOOLS_SCM_DEBUG=true

While we are on the topic of setuptools_scm, I have a method using
venv to upgrade it to 8.1.0, but unfortunately the newer versions do
not honour PYTHONPATH precedence and import the older slackware 15.0
version.  One would have to remove the older system package or use the
venv hack on every slackbuild that requires the newer setuptools_scm
in /opt.  Upstream is aware of this issue but don't have any interest
in fixing it currently.  Hopefully the
python3-setuptools-scm-opt-8.0.2 version continues to work in the
meantime.

> Go for it! It's easier than me trying to merge your changes and submit a PR this week.

Done!