dandi v0.23.0

[regro-cf-autotick-bot]

It is very likely that the current package version for this feedstock is out of date. Notes for merging 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. Checklist before merging this PR:
   • [x] Dependencies have been updated if changed: see upstream
   • [ ] Tests have passed
   • [x] Updated license if changed and license_file is packaged

Note that 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.

NEW: 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 new bot automerge feature to your feedstock!

Closes: #36 Closes: #37

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.

_{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. If you would like a local version of this bot, you might consider using rever. Rever is a tool for automating software releases and forms the backbone of the bot's conda-forge PRing capability. Rever is both conda (conda install -c conda-forge rever) and pip (pip install re-ver) installable. Finally, 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/1005751336, please use this URL for debugging}

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 of the source code shows a discrepancy between the library's imports and the package's stated requirements in the meta.yaml.

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

• packaging
• dandischema
• hdmf
• numpy

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

• girder-client
• email_validator
• pycryptodomex
• jsonschema
• tqdm

[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.

[jwodder]

If I try building this branch locally using conda build with Python 3.8 on Linux, I get the following error:

conda.exceptions.ResolvePackageNotFound:
  - dandischema[version='>=0.2.10,<0.3.0']
  - fscacher
  - etelemetry[version='>=0.2.0']
  - docker-compose
  - pyout[version='>=0.5,!=0.6.0']
  - pyfakefs
  - pynwb[version='>=1.0.3,!=1.1.0']

Yet all of those packages are available in conda-forge. Note, though, that pyout is not available for Python 3.9, though that wouldn't explain why the Python 3.9 builds were previously succeeding.

EDIT: Actually, it appears that the Python 3.9 builds were never succeeding?

[yarikoptic]

re pyout: merged https://github.com/conda-forge/pyout-feedstock/pull/11 which fell behind attention horizon -- it seems to add 3.9 builds

edit: py39 for linux build already listed on https://anaconda.org/conda-forge/pyout/files

[yarikoptic]

If I try building this branch locally using conda build with Python 3.8 on Linux, I get the following error:

I don't have conda build setup locally -- is there -c channel option? then may be -c conda-forge needs to be given?

[jwodder]

@yarikoptic conda build -c conda-forge works. I've pushed a trivial change to the branch; let's see what happens now.

[jwodder]

@yarikoptic The build is still failing for Python 3.9 and all Windows, and when I try building with 3.9 locally, I get the same mess of dependency errors as on the CI. I checked a few of the mentioned packages, and they were all available for Python 3.9.

[satra]

@jwodder - all the windows errors appear to be related to shell completion. should that test be skipped on windows?

[jwodder]

@satra Brief research suggests that process subsitution is just broken on certain older versions of bash on Windows, so I'm going to say "Yes".

[yarikoptic]

0.23.1 should get released with @jwodder's skip on windows, so let's try on that one