dist to pypi as pavics-magpie

[fmigneault]

Blocking Issues

PyPI requires that all dist_require packages are publicly accessible using pip install <pkg>.
Because of this, URL commit/branch references are not permitted.

The package distribution is blocked by the following PR (so new official versions are published) until Mapgie can be pushed as well:

• allow ignoring some arguments for caching key bbangert/beaker#221
• Settings and Improvements authomatic/authomatic#195

Breaking Change

Big downside, INI is not backward compatible.
Because magpie is already taken on PyPI, and that the INI paste deploy loads using the same distribution name, all existing INI file references will have to change their reference to pavics-magpie.

ToDo

If we move on with this change, following must be done:

• update requirements by URL references with pinned versions directly referring to pypi packages.
• update all stack/instances that use an override Magpie INI config
• add important changelog warning
• major version update
• add PYPI_API_TOKEN secret to repo to allow upload of tagged version by CI

[codecov-commenter]

Codecov Report

Merging #518 (cf27f19) into master (27e060a) will increase coverage by 0.00%.
The diff coverage is 70.00%.

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

@@           Coverage Diff           @@
##           master     #518   +/-   ##
=======================================
  Coverage   80.27%   80.27%           
=======================================
  Files          71       71           
  Lines        9615     9616    +1     
  Branches     1323     1323           
=======================================
+ Hits         7718     7719    +1     
  Misses       1597     1597           
  Partials      300      300           

Impacted Files	Coverage Δ
magpie/api/login/__init__.py	100.00% <ø> (ø)
magpie/register.py	48.26% <18.18%> (+<0.01%)	⬆️
magpie/models.py	89.13% <60.00%> (ø)
magpie/api/login/login.py	57.67% <66.66%> (ø)
magpie/ui/utils.py	67.39% <66.66%> (ø)
magpie/services.py	79.52% <71.42%> (ø)
magpie/adapter/magpieservice.py	58.10% <83.33%> (ø)
magpie/__meta__.py	100.00% <100.00%> (ø)
magpie/api/exception.py	93.52% <100.00%> (ø)
magpie/api/management/user/user_utils.py	97.11% <100.00%> (ø)
... and 8 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d2857cb...c7c23eb. Read the comment docs.

[fmigneault]

@dbyrns Because there was a discussion about that recently, I gave a try to publish Magpie to PyPI. I found the issues listed in the PR description. Some of them make me feel it is not worth doing the change because it introduces a breaking change on existing platforms (mounted INI file in dockers).

[dbyrns]

If there is no hard requirement for a pypi package, keeping this as a nice to have is ok.