conda-forge / pluggy-feedstock Goto Github PK

View Code? Open in Web Editor NEW

2.0 8.0 13.0 139 KB

A conda-smithy repository for pluggy.

License: BSD 3-Clause "New" or "Revised" License

pluggy-feedstock's Introduction

About pluggy-feedstock

Feedstock license: BSD-3-Clause

Home: https://github.com/pytest-dev/pluggy

Package license: MIT

Summary: Plugin registration and hook calling for Python

Development: https://github.com/pytest-dev/pluggy/

Documentation: https://pluggy.readthedocs.io/en/latest/

Current build status

All platforms:

Current release info

Name	Downloads	Version	Platforms

Installing pluggy

Installing pluggy from the conda-forge channel can be achieved by adding conda-forge to your channels with:

conda config --add channels conda-forge
conda config --set channel_priority strict

Once the conda-forge channel has been enabled, pluggy can be installed with conda:

conda install pluggy

or with mamba:

mamba install pluggy

It is possible to list all of the versions of pluggy available on your platform with conda:

conda search pluggy --channel conda-forge

or with mamba:

mamba search pluggy --channel conda-forge

Alternatively, mamba repoquery may provide more information:

# Search all versions available on your platform:
mamba repoquery search pluggy --channel conda-forge

# List packages depending on `pluggy`:
mamba repoquery whoneeds pluggy --channel conda-forge

# List dependencies of `pluggy`:
mamba repoquery depends pluggy --channel conda-forge

About conda-forge

conda-forge is a community-led conda channel of installable packages. In order to provide high-quality builds, the process has been automated into the conda-forge GitHub organization. The conda-forge organization contains one repository for each of the installable packages. Such a repository is known as a feedstock.

A feedstock is made up of a conda recipe (the instructions on what and how to build the package) and the necessary configurations for automatic building using freely available continuous integration services. Thanks to the awesome service provided by Azure, GitHub, CircleCI, AppVeyor, Drone, and TravisCI it is possible to build and upload installable packages to the conda-forge anaconda.org channel for Linux, Windows and OSX respectively.

To manage the continuous integration and simplify feedstock maintenance conda-smithy has been developed. Using the conda-forge.yml within this repository, it is possible to re-render all of this feedstock's supporting files (e.g. the CI configuration files) with conda smithy rerender.

For more information please check the conda-forge documentation.

Terminology

feedstock - the conda recipe (raw material), supporting scripts and CI configuration.

conda-smithy - the tool which helps orchestrate the feedstock. Its primary use is in the construction of the CI .yml files and simplify the management of many feedstocks.

conda-forge - the place where the feedstock and smithy live and work to produce the finished article (built conda distributions)

Updating pluggy-feedstock

If you would like to improve the pluggy recipe or build a new package version, please fork this repository and submit a PR. Upon submission, your changes will be run on the appropriate platforms to give the reviewer an opportunity to confirm that the changes result in a successful build. Once merged, the recipe will be re-built and uploaded automatically to the conda-forge channel, whereupon the built conda packages will be available for everybody to install and use from the conda-forge channel. Note that all branches in the conda-forge/pluggy-feedstock are immediately built and any created packages are uploaded, so PRs should be based on branches in forks and branches in the main repository should only be used to build distinct package versions.

In order to produce a uniquely identifiable distribution:

If the version of a package is not being increased, please add or increase the build/number.
If the version of a package is being increased, please remember to return the build/number back to 0.

Feedstock Maintainers

pluggy-feedstock's People

Contributors

Stargazers

Watchers

Forkers

conda-forge-admin nicoddemus jakirkham-feedstocks anacondarecipes berryconda regro-cf-autotick-bot archiconda chrisburr mingwandroid leej3 adriendelsalle bastianzim anaconda-community

pluggy-feedstock's Issues

Pluggy 1.1.0 makes conda fail

Solution to issue cannot be found in the documentation.

I checked the documentation.

Issue

In a clean environment, when update to pluggy 1.1.0:

  Package   Version  Build         Channel         Size
─────────────────────────────────────────────────────────
  Upgrade:
─────────────────────────────────────────────────────────

  - pluggy    1.0.0  pyhd8ed1ab_5  conda-forge
  + pluggy    1.1.0  pyhd8ed1ab_0  conda-forge     21kB

It makes conda unusable in a Mac Apple M2:

KeyError('pkgs_dirs')
Traceback (most recent call last):
  File "/opt/homebrew/Caskroom/miniforge/base/lib/python3.10/site-packages/conda/exception_handler.py", line 16, in __call__
    return func(*args, **kwargs)
  File "/opt/homebrew/Caskroom/miniforge/base/lib/python3.10/site-packages/conda/cli/main.py", line 70, in main_subshell
    p = generate_parser()
  File "/opt/homebrew/Caskroom/miniforge/base/lib/python3.10/site-packages/conda/cli/conda_argparse.py", line 65, in generate_parser
    p = ArgumentParser(
  File "/opt/homebrew/Caskroom/miniforge/base/lib/python3.10/site-packages/conda/cli/conda_argparse.py", line 152, in __init__
    self._subcommands = context.plugin_manager.get_hook_results("subcommands")
  File "/opt/homebrew/Caskroom/miniforge/base/lib/python3.10/site-packages/conda/plugins/manager.py", line 104, in get_hook_results
    (item for items in hook() for item in items),
TypeError: 'NoneType' object is not iterable

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/opt/homebrew/Caskroom/miniforge/base/lib/python3.10/site-packages/conda/exception_handler.py", line 165, in print_unexpected_error_report
    get_main_info_str(error_report["conda_info"])
  File "/opt/homebrew/Caskroom/miniforge/base/lib/python3.10/site-packages/conda/cli/main_info.py", line 250, in get_main_info_str
    info_dict["_" + key] = ("\n" + 26 * " ").join(info_dict[key])
KeyError: 'pkgs_dirs'

# >>>>>>>>>>>>>>>>>>>>>> ERROR REPORT <<<<<<<<<<<<<<<<<<<<<<

    Traceback (most recent call last):
      File "/opt/homebrew/Caskroom/miniforge/base/lib/python3.10/site-packages/conda/exception_handler.py", line 16, in __call__
        return func(*args, **kwargs)
      File "/opt/homebrew/Caskroom/miniforge/base/lib/python3.10/site-packages/conda/cli/main.py", line 70, in main_subshell
        p = generate_parser()
      File "/opt/homebrew/Caskroom/miniforge/base/lib/python3.10/site-packages/conda/cli/conda_argparse.py", line 65, in generate_parser
        p = ArgumentParser(
      File "/opt/homebrew/Caskroom/miniforge/base/lib/python3.10/site-packages/conda/cli/conda_argparse.py", line 152, in __init__
        self._subcommands = context.plugin_manager.get_hook_results("subcommands")
      File "/opt/homebrew/Caskroom/miniforge/base/lib/python3.10/site-packages/conda/plugins/manager.py", line 104, in get_hook_results
        (item for items in hook() for item in items),
    TypeError: 'NoneType' object is not iterable

`$ /opt/homebrew/Caskroom/miniforge/base/bin/conda list`

  environment variables:
conda info could not be constructed.
KeyError('pkgs_dirs')

An unexpected error has occurred. Conda has prepared the above report.

If submitted, this report will be used by core maintainers to improve
future releases of conda.
Would you like conda to send this report to the core maintainers? [y/N]: n

No report sent. To permanently opt-out, use

    $ conda config --set report_errors false

Installed packages

Can't run `conda list`

Environment info

Can't run `conda info`

Version 0.13.1 OSX build failed due to HTTP errors

Latest OSX build isn't available. I'm debugging something that may be tied to version 0.13.0 so I want to see if 0.13.1 fixes something.

Could a @conda-forge/pluggy re-run the build?

Edit: Oh 0.13.1 is just a documentation update. I guess this doesn't matter for my problem, but the build should probably be restarted.