add multiprocessingpandas feedstock #31592

dlaehnemann · 2025-12-01T10:46:36Z

This is a package I would like to use downstream:
bioconda/bioconda-recipes#61008

Locally, it fails with a weird metadata-generation error, where it can't find the file HISTORY.md that is clearly part of this package's repository:
https://github.com/akhtarshahnawaz/multiprocesspandas/blob/v1.1.5/HISTORY.md

Checklist

…eedstock

…thub.com/akhtarshahnawaz/multiprocesspandas/blob/1c459cc969cd939fe9b17ef0fe661f36c30206ce/setup.py#L1

dlaehnemann · 2025-12-01T10:46:52Z

I agree to be listed as a maintainer on this recipe/

github-actions · 2025-12-01T10:48:01Z

Hi! This is the staged-recipes linter and your PR looks excellent! 🚀

conda-forge-admin · 2025-12-01T10:48:18Z

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 (recipes/multiprocesspandas/meta.yaml) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipes/multiprocesspandas/meta.yaml:

ℹ️ noarch: python recipes should usually follow the syntax in our documentation for specifying the Python version.
- For the host section of the recipe, you should usually use the pin python {{ python_min }} for the python entry.
- For the run section of the recipe, you should usually use the pin python >={{ python_min }} for the python entry.
- For the test.requires section of the recipe, you should usually use the pin python {{ python_min }} for the python entry.
- If the package requires a newer Python version than the currently supported minimum version on conda-forge, you can override the python_min variable by adding a Jinja2 set statement at the top of your recipe (or using an equivalent context variable for v1 recipes).

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/19825999455. Examine the logs at this URL for more detail.}

…iprocessingpandas recipe to work

dlaehnemann · 2025-12-01T14:05:40Z

OK, I think I understand the problem now. Just documenting this if others come across similar issues. The error was:

  Running command Preparing metadata (pyproject.toml)
  Traceback (most recent call last):
    File "/home/conda/staged-recipes/build_artifacts/multiprocesspandas_1764586377465/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_pl/lib/python3.14/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 389, in <module>
      main()
      ~~~~^^
    File "/home/conda/staged-recipes/build_artifacts/multiprocesspandas_1764586377465/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_pl/lib/python3.14/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 373, in main
      json_out["return_val"] = hook(**hook_input["kwargs"])
                               ~~~~^^^^^^^^^^^^^^^^^^^^^^^^
    File "/home/conda/staged-recipes/build_artifacts/multiprocesspandas_1764586377465/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_pl/lib/python3.14/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 175, in prepare_metadata_for_build_wheel
      return hook(metadata_directory, config_settings)
    File "/home/conda/staged-recipes/build_artifacts/multiprocesspandas_1764586377465/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_pl/lib/python3.14/site-packages/setuptools/build_meta.py", line 374, in prepare_metadata_for_build_wheel
      self.run_setup()
      ~~~~~~~~~~~~~~^^
    File "/home/conda/staged-recipes/build_artifacts/multiprocesspandas_1764586377465/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_pl/lib/python3.14/site-packages/setuptools/build_meta.py", line 512, in run_setup
      super().run_setup(setup_script=setup_script)
      ~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^
    File "/home/conda/staged-recipes/build_artifacts/multiprocesspandas_1764586377465/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_pl/lib/python3.14/site-packages/setuptools/build_meta.py", line 317, in run_setup
      exec(code, locals())
      ~~~~^^^^^^^^^^^^^^^^
    File "<string>", line 6, in <module>
  FileNotFoundError: [Errno 2] No such file or directory: 'HISTORY.md'
  error: subprocess-exited-with-error
  
  × Preparing metadata (pyproject.toml) did not run successfully.
  │ exit code: 1
  ╰─> No available output.

Basically, the (empty) file HISTORY.md was being used by the setup.py script, but was not bundled in the PyPi tarball. So for this recipe, the solution I chose is to remove the usage of HISTORY.md from the setup.py used for the conda-forge build with a patch. Especially, as this package hasn't been updated in years, so I don't expect much renewed activity that might rely on this HISTORY.md file in the future...

Here's how patches work, in case anybody is looking how to do this:

Download the tarball that the recipe uses.
Unpack it.
Start a git repository from it by cding into the directory and running git init.
git add * everything, and git commit -m "initial commit" to start tracking everything.
Edit the files that need editing.
Commit these changes (git add --update and `git commit -m "meaningful commit message").
Create a patch from this with git format-patch -1 HEAD.
Provide this to the recipe via the respective conda recipe syntax for patches

dlaehnemann · 2025-12-01T14:21:56Z

Seems like a download failure for the linter, so I'll just try a restart:

@conda-forge-admin, please restart ci

dlaehnemann · 2025-12-01T14:24:00Z

Ah, and just for cross-referencing and thanks: this is the other pull request where I got the relevant pointers on the FileNotFound error.

dlaehnemann · 2025-12-01T14:25:02Z

Hmm, failed again. Will try once more:

@conda-forge-admin, please restart ci

conda-forge-admin · 2025-12-01T14:35:28Z

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 (recipes/multiprocesspandas/meta.yaml) and found it was in an excellent condition.

dlaehnemann · 2025-12-01T14:45:24Z

All of the current failures seem to be download issues for conda installations:

critical libmamba Multiple errors occured:
    Download error (28) Timeout was reached [https://conda.anaconda.org/conda-forge/noarch/repodata.json.zst]
    Operation too slow. Less than 30 bytes/sec transferred the last 60 seconds

So I guess it is worth re-trying in a bit.

dlaehnemann · 2025-12-01T14:54:17Z

@conda-forge-admin, please restart ci

This leads to unsolvable dependencies, as the runtime environment needs an older python version. This reverts commit c8eb463.

conda-forge-admin · 2025-12-01T15:07:49Z

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 (recipes/multiprocesspandas/meta.yaml) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipes/multiprocesspandas/meta.yaml:

ℹ️ noarch: python recipes should usually follow the syntax in our documentation for specifying the Python version.
- For the host section of the recipe, you should usually use the pin python {{ python_min }} for the python entry.
- For the run section of the recipe, you should usually use the pin python >={{ python_min }} for the python entry.
- For the test.requires section of the recipe, you should usually use the pin python {{ python_min }} for the python entry.
- If the package requires a newer Python version than the currently supported minimum version on conda-forge, you can override the python_min variable by adding a Jinja2 set statement at the top of your recipe (or using an equivalent context variable for v1 recipes).

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/19836717007. Examine the logs at this URL for more detail.}

dlaehnemann · 2025-12-01T15:09:48Z

The linter now still fails with:

Install environment `lint`
  /home/runner/micromamba-bin/micromamba create -y -r /home/runner/micromamba -n lint conda-smithy pygithub requests pixi --log-level warning --rc-file /home/runner/work/_temp/setup-micromamba/.condarc
  warning  libmamba Download error (28) Timeout was reached [https://conda.anaconda.org/conda-forge/noarch/repodata.json.zst]
      Operation too slow. Less than 30 bytes/sec transferred the last 60 seconds
  warning  libmamba Download error (28) Timeout was reached [https://conda.anaconda.org/conda-forge/noarch/repodata.json.zst]
      Operation too slow. Less than 30 bytes/sec transferred the last 60 seconds
  critical libmamba Multiple errors occurred:
      Download error (28) Timeout was reached [https://conda.anaconda.org/conda-forge/noarch/repodata.json.zst]
      Operation too slow. Less than 30 bytes/sec transferred the last 60 seconds
      Subdir conda-forge/noarch not loaded!
      If you run into this error repeatedly, your package cache may be corrupted.
      Please try running `mamba clean -a` to remove this cache before retrying the operation.
      
      If you still are having issues, please report the error on `mamba-org/mamba`'s issue tracker:
      https://github.com/mamba-org/mamba/issues/new?assignees=&labels=&projects=&template=bug.yml
  Error: The process '/home/runner/micromamba-bin/micromamba' failed with exit code 1

dlaehnemann · 2025-12-01T15:40:51Z

@conda-forge-admin, please restart ci

dlaehnemann · 2025-12-01T16:26:31Z

Different stuff just seems to randomly fail with conda-related issues on every restart. Currently it is the osx_64 build with:

Configuring conda
+ cat
+ source /Users/runner/miniforge3/etc/profile.d/conda.sh
/Users/runner/work/1/s/.scripts/run_osx_build.sh: line 48: /Users/runner/miniforge3/etc/profile.d/conda.sh: No such file or directory
+ conda activate base
/Users/runner/work/1/s/.scripts/run_osx_build.sh: line 49: conda: command not found
+ echo -e '\n\nSetting up the condarc and mangling the compiler.'


Setting up the condarc and mangling the compiler.
+ setup_conda_rc ./ ./recipes ./.ci_support/osx64.yaml
/Users/runner/work/1/s/.scripts/run_osx_build.sh: line 52: setup_conda_rc: command not found
+ [[ azure != '' ]]
+ mangle_compiler ./ ./recipes .ci_support/osx64.yaml
/Users/runner/work/1/s/.scripts/run_osx_build.sh: line 54: mangle_compiler: command not found
+ [[ azure != '' ]]
+ echo -e '\n\nMangling homebrew in the CI to avoid conflicts.'
+ /usr/bin/sudo mangle_homebrew


Mangling homebrew in the CI to avoid conflicts.
sudo: mangle_homebrew: command not found
+ /usr/bin/sudo -k
+ echo -e '\n\nRunning the build setup script.'
+ source run_conda_forge_build_setup


Running the build setup script.
/Users/runner/work/1/s/.scripts/run_osx_build.sh: line 66: run_conda_forge_build_setup: No such file or directory
+ set -e
+ mkdir -p /Users/runner/bld/osx-64/ /Users/runner/bld/osx-arm64/ /Users/runner/bld/noarch/
+ test -f /Users/runner/bld/noarch/repodata.json
+ conda index /Users/runner/bld
/Users/runner/work/1/s/.scripts/run_osx_build.sh: line 74: conda: command not found

dlaehnemann · 2025-12-01T20:30:46Z

@conda-forge-admin, please restart ci

dlaehnemann · 2025-12-01T20:35:09Z

@conda-forge-admin, please restart ci

dlaehnemann added 2 commits December 1, 2025 10:39

add initial grayskull-generated meta.yaml for multiprocessingpandas f…

80fa49e

…eedstock

fix: add undocumented setuptools requirement for building: https://gi…

f27bd4b

…thub.com/akhtarshahnawaz/multiprocesspandas/blob/1c459cc969cd939fe9b17ef0fe661f36c30206ce/setup.py#L1

dlaehnemann mentioned this pull request Dec 1, 2025

add howard ann recipe bioconda/bioconda-recipes#61008

Draft

dlaehnemann mentioned this pull request Dec 1, 2025

publish latest version on PyPi bioinfo-chru-strasbourg/howard#457

Open

fix: add patch to remove empty HISTORY.md file from setup.py for mult…

61c8cb3

…iprocessingpandas recipe to work

conda-forge-webservices bot closed this Dec 1, 2025