conda-forge / importlib_resources-feedstock

A conda-smithy repository for importlib_resources.

About importlib_resources-feedstock

Feedstock license: BSD-3-Clause

Home: http://importlib-resources.readthedocs.io

Package license: Apache-2.0

Summary: Backport of Python 3.7's standard library importlib.resources

Current build status

All platforms:

Current release info

Name	Downloads	Version	Platforms

Installing importlib_resources

Installing importlib_resources 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, importlib-resources, importlib_resources can be installed with conda:

conda install importlib-resources importlib_resources

or with mamba:

mamba install importlib-resources importlib_resources

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

conda search importlib-resources --channel conda-forge

or with mamba:

mamba search importlib-resources --channel conda-forge

Alternatively, mamba repoquery may provide more information:

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

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

# List dependencies of `importlib-resources`:
mamba repoquery depends importlib-resources --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 importlib_resources-feedstock

If you would like to improve the importlib_resources 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/importlib_resources-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

• @ocefpaf

importlib_resources-feedstock's Issues

@conda-forge-admin, please remove bot automerge

Additional comment:

No response

auto-merge bot

@conda-forge-admin, please add bot automerge

[warning] failed package validation and/or copy for commit 0166bde5be402b92033350a857480555a84b87e1

Hi @conda-forge/importlib_resources! This is the friendly automated conda-forge-webservice!

It appears that one or more of your feedstock's outputs is either invalid or
did not copy from the staging channel (cf-staging) to the production channel (conda-forge). :(

This failure can happen for a lot of reasons, including an outdated feedstock
token, a feedstock output that is not allowed for that feedstock, or a feedstock output
with files that are not allowed for that output. Below we have put some information
about the failure to help you debug it.

Rerendering the feedstock will usually fix these problems.

If you have any issues or questions, you can find us on gitter in the
community chat room or you can bump us right here.

error messages:

• invalid md5 sum for artifact https://conda.anaconda.org/cf-staging/win-64/importlib_resources-5.1.2-py39hcbf5309_0.tar.bz2

Latest version not compatible with Python 3.6

Solution to issue cannot be found in the documentation.

• I checked the documentation.

Issue

This package should require python >=3.7 since 5.5.0: https://importlib-resources.readthedocs.io/en/latest/history.html#v5-5-0

With 5.10 and Python 3.6, I get the error AttributeError: 'str' object has no attribute '__spec__'. This was reported python/importlib_resources#271

The recipe should be updated to require python>=3.7.
To avoid the Python 3.6 issue, it would be nice to patch the repodata.

Installed packages

importlib-metadata        4.8.1            py36h5fab9bb_0    conda-forge
importlib_metadata        4.8.1                hd8ed1ab_1    conda-forge
importlib_resources       5.10.1             pyhd8ed1ab_0    conda-forge
...
python                    3.6.15          hb7a2778_0_cpython    conda-forge

Environment info

active environment : base
    active env location : /opt/conda
            shell level : 1
       user config file : /root/.condarc
 populated config files : /opt/conda/.condarc
          conda version : 22.9.0
    conda-build version : not installed
         python version : 3.10.6.final.0
       virtual packages : __linux=5.15.49=0
                          __glibc=2.31=0
                          __unix=0=0
                          __archspec=1=x86_64
       base environment : /opt/conda  (writable)
      conda av data dir : /opt/conda/etc/conda
  conda av metadata url : None
           channel URLs : https://conda.anaconda.org/conda-forge/linux-64
                          https://conda.anaconda.org/conda-forge/noarch
          package cache : /opt/conda/pkgs
                          /root/.conda/pkgs
       envs directories : /opt/conda/envs
                          /root/.conda/envs
               platform : linux-64
             user-agent : conda/22.9.0 requests/2.28.1 CPython/3.10.6 Linux/5.15.49-linuxkit ubuntu/20.04.5 glibc/2.31
                UID:GID : 0:0
             netrc file : None
           offline mode : False

@conda-forge-admin, please add bot automerge

@conda-forge-admin, please add bot automerge

Mismatching importlib-resources and importlib_resources

Over on conda-forge/jupyter-book-feedstock#10 , seeing a fail when an env resolves with two versions of the twins:
logs

    importlib-resources:           3.3.1-pyhd8ed1ab_0        conda-forge
    importlib_resources:           5.4.0-pyhd8ed1ab_0        conda-forge

whcih then yields a bunch of clobber warnings.

I guess I'll pin both for now, but seems potentially problematic.