Are we going to distribute a PyPI package? What should be included?

[turbomam]

• [ ] restore the src/mixs/datamodel/__init__.py as described below
• [ ] Are we going to distribute a PyPI package? https://pypi.org/project/mixs-linkml/ ?
• [ ] What extras should be included, like the schema YAML file?
• [ ] We will need to set up PyPI authentication

The Python representation of the MIxS standard is in src/mixs/datamodel/mixs.py

@sujaypatil96 has added some doc-generating utilities to src/scripts

[turbomam]

Neither of those paths have an __init__.py file at this time

[turbomam]

src/mixs_6_2_for_merge/datamodel/__init__.py (as an example)

from .mixs_6_2_for_merge import *

[turbomam]

PyPI package build and publishing are included in the default GH actions, but we need to decide whose PyPI account to use and save the credential as a password

Or we can use a project-specific credential

otherwise:

ERROR HTTPError: 403 Forbidden from https://upload.pypi.org/legacy/
Invalid or non-existent authentication information. See
https://pypi.org/help/#invalid-auth for more information.

[sujaypatil96]

Should we make this a priority for the next release, perhaps v7.0?

[turbomam]

see also this, and more

• https://github.com/GenomicsStandardsConsortium/mixs/issues/245

[turbomam]

The release of a PyPI artifact (which will make it easier for people to interact with MIxS programmatically) could be considered orthogonal to MIxS 7, which I mainly think of a s new content.

But maybe it is advantageous to time the PyPI package with MIxS, 7, so that it gets a lot of visibility?

It would be helpful to know what MIxS 7's ETA is.