Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 84.12%. Comparing base (1bf919a) to head (94d04ae).
Report is 10 commits behind head on develop.

@@           Coverage Diff            @@
##           develop     #523   +/-   ##
========================================
  Coverage    84.12%   84.12%           
========================================
  Files           26       26           
  Lines         8122     8122           
  Branches      1697     1697           
========================================
  Hits          6833     6833           
  Misses        1289     1289           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

What is the purpose of having (or not having) TestPyPI package?

The test.pypi.org repo is only meant to test the upload works properly. The packages inside are not meant to be relied upon. An issue mentioned is that if you point it to install from there, the dependencies are not searched for from the normal pypi repo, which would naturally fail because numpy2.x is not available.

The test.pypi.org repo is only meant to test the upload works properly.

For example, is it enough to write "please don't install spglib from test.pypi" at https://test.pypi.org/project/spglib/ ?

For example, is it enough to write "please don't install spglib from test.pypi" at https://test.pypi.org/project/spglib/ ?

I think rather not mention anything and keep the documentation minimal. The concept of test.pypi will gradually fade away, and when needed it is easier to write a quick comment to an issue. Alternatively, we could point them to upstream pip documentation?

Alternatively, we could point them to upstream pip documentation?

This is beyond my ability to comment.

Alternatively, we could point them to upstream pip documentation?

This is beyond my ability to comment.

For reference: https://pip.pypa.io/en/stable/cli/pip_install/