Get up on PIP and Conda about mt_metadata

[kujaku11]

@lheagy Any chance you could bump the current version to 0.1.1. I think there has been a good amount of development to warrant a bump. I completed 2 PR's #19 and #29. @kkappler agree?

[lheagy]

@kujaku11: do you have an account on the test pypi and pypi sites?

• test: https://test.pypi.org/account/register/
• pypi: https://pypi.org/account/register/

Would you mind sharing those with me? (here or on slack is fine)

[kkappler]

Go for it. This seems to be partially blocked by some security issues on Jared's work machine ... how to get around this in general?

[lheagy]

It looks like 0.1.1 was released on May 12? https://github.com/kujaku11/mt_metadata/releases/tag/v0.1.1

should I bump to 0.1.2?

[lheagy]

ah, although it doesn't look like it was released on pypi. I will upload there. Just let me know if you also want to bump to 0.1.2

[kujaku11]

@lheagy Let's wait on the bump version release for a second, I want to pull updates into main and then we can release that as 0.1.1?

[kujaku11]

@lheagy We just did the pull request and all tests pass. We can go ahead an release the main as either 0.1.1 or bump it to 0.1.2. In the pull request I added your update of the setup.py file, so it is now in the main branch.

[lheagy]

sounds good -- I will get that done today

[brunorpinho]

PyPI is behind this repo so the package you get when you pip install mt_metadata doesn't play well with the rest of the ecosystem (but they both installs the same version - 0.1.7).
Temp fix:
pip install git+https://github.com/kujaku11/mt_metadata.git

Most of the differences are in the transfer_function.tf.standard jsons