Migrate from setuptools to hatchling

[maresb]

Base: #1371

Change the build-backend from setuptools to hatchling.

Question: Is there any reason for docs/ to be included in the sdist? It's not in the wheel.

For some reason I'm having trouble including the file aesara/d3viz/html/template.html. I'm not sure yet why it's being excluded.

Thank you for opening a PR!

Here are a few important guidelines and requirements to check before your PR can be merged:

• There is an informative high-level description of the changes.
• The description and/or commit message(s) references the relevant GitHub issue(s).
• pre-commit is installed and set up.
• The commit messages follow these guidelines.
• The commits correspond to relevant logical changes, and there are no commits that fix changes introduced by other commits in the same branch/BR.
• There are tests covering the changes introduced in the PR.

Don't worry, your PR doesn't need to be in perfect order to submit it. As development progresses and/or reviewers request changes, you can always rewrite the history of your feature/PR branches.

If your PR is an ongoing effort and you would like to involve us in the process, simply make it a draft PR.

[codecov]

Codecov Report

Merging #1384 (cce4fa5) into main (d789a5f) will decrease coverage by 0.02%.
The diff coverage is n/a.

❗ Current head cce4fa5 differs from pull request most recent head 051652b. Consider uploading reports for the commit 051652b to get more accurate results

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1384      +/-   ##
==========================================
- Coverage   74.71%   74.69%   -0.02%     
==========================================
  Files         194      194              
  Lines       49826    49730      -96     
  Branches    10539    10527      -12     
==========================================
- Hits        37226    37145      -81     
+ Misses      10272    10262      -10     
+ Partials     2328     2323       -5     

Impacted Files	Coverage Δ
aesara/tensor/special.py	90.64% <0.00%> (-0.27%)	⬇️
aesara/tensor/math.py	90.39% <0.00%> (-0.04%)	⬇️
aesara/tensor/inplace.py	100.00% <0.00%> (ø)
aesara/scalar/math.py	85.29% <0.00%> (+0.29%)	⬆️

[maresb]

Ok, I think I got it!!! Excludes are now determined by the root /.gitignore union additional excludes from pyproject.toml. The last few missing files were caused by a few /.gitignore rules that were too broad.

Unlike my previous PRs, once #1371 is merged I want to do a "squash and merge" here, so I'm not curating my individual commits.

[maresb]

Rebased on latest changes. All tests were green.

[maresb]

I made another review pass since I hadn't yet checked the wheel. The bin/ directory was missing from the wheel, so I reincluded it. I'm feeling fairly confident now that I've done due diligence here.

[maresb]

[deleted, wrong PR]

[maresb]

Still open question: Is there any reason for docs/ to be included in the sdist? It's not in the wheel, and it takes up significant space.

[brandonwillard]

Still open question: Is there any reason for docs/ to be included in the sdist? It's not in the wheel, and it takes up significant space.

Good question; I'm not aware of one at the moment, so we can probably remove it.

[maresb]

Still open question: Is there any reason for docs/ to be included in the sdist? It's not in the wheel, and it takes up significant space.

Good question; I'm not aware of one at the moment, so we can probably remove it.

Great, let's do it in the next PR though. (One thing at a time.)

[maresb]

Thanks for the approval!

Interesting... if I update the branch with a rebase (via the GH interface), then it discards your approving review. But with a merge update, it retains your approval. (Since I ultimately want to squash-and-merge, the Git history will remain linear.)

[maresb]

Addendum

This PR broke nightly builds because it didn't adapt the key names for hatch-vcs. See #1406 for the issue and #1407 for the fix.