Python Version Bumps & New Pacakges

[teaguesterling]

This is a collection of version bumps and other minor maintenance activities for some python packages. The purpose of these is in preparation for another package that I plan to add soon that has very specific version requirements and I would like to separate these simpler updates from that larger package.

Packages with just newer versions added:

• py-aiohttp
• py-azure-mgmt-storage
• py-nest-asyncio
• py-uvloop

Packages with new versions added and dependencies updated:

• py-orjson

Packages with new and at least one older package added for compatibility with py-hail (in the future):

• py-rich
• py-humanize

Packages with an older version added for compatibility with py-hail (in the future):

• py-python-json-logger

Packages with older versions conflicts based on documentation and observed failures:

• py-maturin

New packages added:

• py-jproperties (required for py-hail)
• py-janus (required for py-hail)

Note: The py-maturin dependencies in py-orjson and the py-maturin rust dependencies could probably be made more specific, but considering their documentation now recommends >=1,<2 it seemed reasonable to deprecate the v0 versions.

[spackbot-app]

Hi @teaguesterling! I noticed that the following package(s) don't yet have maintainers:

• py-aiohttp
• py-azure-mgmt-storage
• py-humanize
• py-maturin
• py-nest-asyncio
• py-orjson
• py-python-json-logger
• py-rich
• py-uvloop

Are you interested in adopting any of these package(s)? If so, simply add the following to the package class:

    maintainers("teaguesterling")

If not, could you contact the developers of this package and see if they are interested? You can quickly see who has worked on a package with spack blame:

$ spack blame py-aiohttp

Thank you for your help! Please don't add maintainers without their consent.

You don't have to be a Spack expert or package developer in order to be a "maintainer," it just gives us a list of users willing to review PRs or debug issues relating to this package. A package can have multiple maintainers; just add a list of GitHub handles of anyone who wants to volunteer.

[teaguesterling]

This was split up into multiple PRs