Register BERtron client module in PyPI #7
Description
Issue migrated from ber-data/bertron repo.
The Python client module will need to be publicly available in order for it to be used in the Jupyter notebook. The bertron-mcp server will also rely on the client module.
Questions:
Are we ready to make the client module publicly available?
Should we split the client module off into a separate repo or keep it here?
Would this impact the API versioning? (i.e., mismatches between client and API version numbers)
Can the current build workflow push just the client portion of this repo into PyPI?
Shreyas comment: We can use git instead of pypi for this. We still need to package the module, but it might be easier to just do this against the github repo as a starting point.
Eric comment: I also would prefer using git at this stage. Example (showing how this repo currently references the schema repo:
https://github.com/ber-data/bertron/blob/4623d9f1ab049919879075a4ce780b7073a1ad67/pyproject.toml#L24