pymc v4.0.1

[regro-cf-autotick-bot]

It is very likely that the current package version for this feedstock is out of date.

Checklist before merging this PR:

• [ ] Dependencies have been updated if changed: see upstream
• [ ] Tests have passed
• [ ] Updated license if changed and license_file is packaged

Information about this PR:

1. Feel free to push to the bot's branch to update this PR if needed.
2. The bot will almost always only open one PR per version.
3. The bot will stop issuing PRs if more than 3 version bump PRs generated by the bot are open. If you don't want to package a particular version please close the PR.
4. If you want these PRs to be merged automatically, make an issue with code>@conda-forge-admin,</codeplease add bot automerge in the title and merge the resulting PR. This command will add our bot automerge feature to your feedstock.
5. If this PR was opened in error or needs to be updated please add the bot-rerun label to this PR. The bot will close this PR and schedule another one. If you do not have permissions to add this label, you can use the phrase code>@<space/conda-forge-admin, please rerun bot in a PR comment to have the conda-forge-admin add it for you.

Pending Dependency Version Updates

Here is a list of all the pending dependency version updates for this repo. Please double check all dependencies before merging.

Name	Upstream Version	Current Version
mkl-service	2.4.0.post1
pymc	4.0.1

Dependency Analysis

Please note that this analysis is highly experimental. The aim here is to make maintenance easier by inspecting the package's dependencies. Importantly this analysis does not support optional dependencies, please double check those before making changes. If you do not want hinting of this kind ever please add bot: inspection: false to your conda-forge.yml. If you encounter issues with this feature please ping the bot team conda-forge/bot.

Analysis by source code inspection shows a discrepancy between it and the the package's stated requirements in the meta.yaml.

Packages found by source code inspection but not in the meta.yaml:

• xarray
• typing_extensions
• jax

Packages found in the meta.yaml but not found by source code inspection:

• mkl-service
• typing-extensions

_{This PR was created by the regro-cf-autotick-bot. The regro-cf-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. Feel free to drop us a line if there are any issues! This PR was generated by https://github.com/regro/autotick-bot/actions/runs/2532034606, please use this URL for debugging.}

[regro-cf-autotick-bot]

Hi! This feedstock was not able to be rerendered after the version update changes. I have pushed the version update changes anyways and am trying to rerender again with this comment. Hopefully you all can fix this!

@conda-forge-admin rerender

[conda-forge-linter]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

[github-actions[bot]]

Hi! This is the friendly automated conda-forge-webservice.

I tried to rerender for you but ran into some issues. Please check the output logs of the latest rerendering GutHub actions workflow run for errors. You can also ping conda-forge/core for further assistance or try re-rendering locally.

This message was generated by GitHub actions workflow run https://github.com/conda-forge/pymc-feedstock/actions/runs/2532181685.

[twiecki]

@maresb any idea why it's failing?

[twiecki]

Did we not update aesara dependencies?

[ricardoV94]

Did we not update aesara dependencies?

We did

[twiecki]

Then it needs to be updated here as well. Not sure if that should have happened automatically?

[ricardoV94]

Then it needs to be updated here as well. Not sure if that should have happened automatically?

Perhaps not... that is a bit of a PITA going forward as we are pinning individual aeppl / aesara versions due to their fast-changing cycles at the moment

[twiecki]

Perhaps not... that is a bit of a PITA going forward as we are pinning individual aeppl / aesara versions due to their fast-changing cycles at the moment

No I meant that this recipe should grab it from pymc requirements.txt.

[ricardoV94]

@twiecki merge?

[maresb]

No I meant that this recipe should grab it from pymc requirements.txt.

@twiecki, one would hope, but that's unfortunately not the case. The difficulty lies in the fact that there is no standardized way to inspect the dependencies of a given package. There are multiple package build backends, e.g. Setuptools and Poetry, and each has their own system...

Poetry stores dependencies in pyproject.toml under [tool.poetry.dependencies]. On the other hand, Setuptools gets its dependencies from the install_requires argument in setup.py, which is traditionally read from a requirements.txt, but allows for arbitrary code execution. Therefore, things must be handled on a case-by-case basis.

The current state-of-the-art is a bot which tries to automatically infer the dependencies:

@conda-grayskull show requirements

[conda-grayskull]

Working on your request...

[maresb]

Seems to have choked, but that's no surprise because it's very experimental, and this is a multi-output recipe now.

The backend of this tool is Grayskull which has an online interface here: https://marcelotrevisani.info:8000/recipe/?name=pymc

Up to indentation and removing >=3.7 from - python >=3.7, you can copy-paste the requirements from there.