conda-forge / pydantic-feedstock

A conda-smithy repository for pydantic.

About pydantic-feedstock

Feedstock license: BSD-3-Clause

Home: https://github.com/pydantic/pydantic

Package license: MIT

Summary: Data validation and settings management using python type hinting

Development: https://github.com/pydantic/pydantic

Documentation: https://docs.pydantic.dev

Data validation and settings management using python type hinting. See documentation https://docs.pydantic.dev for more details.

Current build status

All platforms:

Current release info

Name	Downloads	Version	Platforms

Installing pydantic

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

conda install pydantic

or with mamba:

mamba install pydantic

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

conda search pydantic --channel conda-forge

or with mamba:

mamba search pydantic --channel conda-forge

Alternatively, mamba repoquery may provide more information:

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

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

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

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

• @davidbrochart
• @dgasmith
• @pavelzw
• @samuelcolvin

pydantic-feedstock's Issues

Add extra dependencies to recipe

I am attempting to add a recipe to conda-forge that depends on pydantic with the [email] extra. However, conda does not support extras, and email-validator is not listed as a runtime dependency in pydantic's conda-forge recipe. I would like to request that email-validator (and python-dotenv, for completeness) be added to the runtime dependencies in pydantic's conda-forge recipe so that they will be available to packages that depend on pydantic. (The alternative course of action, in which projects that need extras explicitly list the packages in the extras in their recipes, would shift responsibility for keeping pydantic's dependencies up to date from the maintainers of this recipe to the maintainters of all recipes that depend on pydantic, which seems undesirable.)

Need `annotated-types` and `pydantic-core` recipe for upcoming 2.0

Comment:

The big pydantic_core refactor split out one of the submodules into its own package, which I don't think has been packaged onto conda-forge yet.

pydantic/pydantic#4516
pydantic/pydantic#4804

https://pypi.org/project/annotated-types/
https://github.com/annotated-types/annotated-types

conda-forge/staged-recipes#21536

Manual update 1.10.8

Additional comment:

@conda-forge-admin please rerender

Can't install on python 3.7

Same as discussed on #1.

When trying to install pydantic with conda, it either tells me I have to downgrade to python 3.6, or if I force 3.7 it refuses due to dataclasses constraints.

Is there anything that can be done about this or is this a limition of conda?

➤  docker run -it --rm continuumio/miniconda3 bash
(base) root@3ab1394d034f:/# conda install pydantic -c conda-forge
Solving environment: done

## Package Plan ##

  environment location: /opt/conda

  added / updated specs: 
    - pydantic


The following packages will be downloaded:

    package                    |            build
    ---------------------------|-----------------
    openssl-1.0.2p             |    h14c3975_1002         3.1 MB  conda-forge
    requests-2.21.0            |        py36_1000          84 KB  conda-forge
    cryptography-2.3.1         |py36hb7f436b_1000         593 KB  conda-forge
    pycparser-2.19             |             py_0          87 KB  conda-forge
    pycosat-0.6.3              |py36h14c3975_1001         104 KB  conda-forge
    pip-18.1                   |        py36_1000         1.8 MB  conda-forge
    cffi-1.11.5                |py36h9745a5d_1001         211 KB  conda-forge
    wheel-0.32.3               |           py36_0          34 KB  conda-forge
    python-3.6.6               |    hd21baee_1003        29.0 MB  conda-forge
    ca-certificates-2018.11.29 |       ha4d7672_0         143 KB  conda-forge
    ruamel_yaml-0.15.71        |py36h14c3975_1000         257 KB  conda-forge
    six-1.12.0                 |        py36_1000          22 KB  conda-forge
    chardet-3.0.4              |        py36_1003         190 KB  conda-forge
    urllib3-1.24.1             |        py36_1000         148 KB  conda-forge
    conda-4.5.12               |        py36_1000         653 KB  conda-forge
    dataclasses-0.6            |             py_0          15 KB  conda-forge
    pysocks-1.6.8              |        py36_1002          22 KB  conda-forge
    pyopenssl-18.0.0           |        py36_1000          80 KB  conda-forge
    idna-2.8                   |        py36_1000         132 KB  conda-forge
    pydantic-0.18.2            |             py_0          35 KB  conda-forge
    asn1crypto-0.24.0          |        py36_1003         154 KB  conda-forge
    certifi-2018.11.29         |        py36_1000         145 KB  conda-forge
    setuptools-40.6.3          |           py36_0         631 KB  conda-forge
    ------------------------------------------------------------
                                           Total:        37.6 MB

The following NEW packages will be INSTALLED:

    dataclasses:     0.6-py_0               conda-forge
    pydantic:        0.18.2-py_0            conda-forge

The following packages will be UPDATED:

    asn1crypto:      0.24.0-py37_0                      --> 0.24.0-py36_1003          conda-forge
    ca-certificates: 2018.03.07-0                       --> 2018.11.29-ha4d7672_0     conda-forge
    certifi:         2018.11.29-py37_0                  --> 2018.11.29-py36_1000      conda-forge
    cffi:            1.11.5-py37he75722e_1              --> 1.11.5-py36h9745a5d_1001  conda-forge
    chardet:         3.0.4-py37_1                       --> 3.0.4-py36_1003           conda-forge
    conda:           4.5.12-py37_0                      --> 4.5.12-py36_1000          conda-forge
    idna:            2.8-py37_0                         --> 2.8-py36_1000             conda-forge
    pip:             18.1-py37_0                        --> 18.1-py36_1000            conda-forge
    pycosat:         0.6.3-py37h14c3975_0               --> 0.6.3-py36h14c3975_1001   conda-forge
    pycparser:       2.19-py37_0                        --> 2.19-py_0                 conda-forge
    pyopenssl:       18.0.0-py37_0                      --> 18.0.0-py36_1000          conda-forge
    pysocks:         1.6.8-py37_0                       --> 1.6.8-py36_1002           conda-forge
    requests:        2.21.0-py37_0                      --> 2.21.0-py36_1000          conda-forge
    ruamel_yaml:     0.15.46-py37h14c3975_0             --> 0.15.71-py36h14c3975_1000 conda-forge
    setuptools:      40.6.3-py37_0                      --> 40.6.3-py36_0             conda-forge
    six:             1.12.0-py37_0                      --> 1.12.0-py36_1000          conda-forge
    urllib3:         1.24.1-py37_0                      --> 1.24.1-py36_1000          conda-forge
    wheel:           0.32.3-py37_0                      --> 0.32.3-py36_0             conda-forge

The following packages will be DOWNGRADED:

    cryptography:    2.4.2-py37h1ba5d50_0               --> 2.3.1-py36hb7f436b_1000   conda-forge
    openssl:         1.1.1a-h7b6447c_0                  --> 1.0.2p-h14c3975_1002      conda-forge
    python:          3.7.1-h0371630_7                   --> 3.6.6-hd21baee_1003       conda-forge

Proceed ([y]/n)? n


CondaSystemExit: Exiting.

(base) root@3ab1394d034f:/# conda install python=3.7 pydantic -c conda-forge
Solving environment: failed

UnsatisfiableError: The following specifications were found to be in conflict:
  - pydantic -> dataclasses[version='>=0.6'] -> python[version='>=3.6,<3.7'] -> readline=6.2
  - pydantic -> dataclasses[version='>=0.6'] -> python[version='>=3.6,<3.7'] -> sqlite=3.13
  - pydantic -> dataclasses[version='>=0.6'] -> python[version='>=3.6,<3.7'] -> tk=8.5
  - python=3.7
Use "conda info <package>" to see the dependencies for each package.

Possibly package release 1.10.17

Comment:

Release 1.10.17 has a nice little trick (from pydantic.v1 import ... being available in the v1 API) which helps packages that needs to support both versions at install time.

https://docs.pydantic.dev/latest/changelog/#v11017-2024-06-20

I didn't see discussion on this so I'm just planting a flag - happy to see somebody else do this, or I'll do it in the next week or so

Similar to #89

Looks like a good starting point #125

Consider releasing pydantic 1.10.11

Comment:

Its latest release of the 1.x series and may help with the transition

https://github.com/pydantic/pydantic/releases/tag/v1.10.11

(My attempt:

@conda-forge-admin please rerender

)

How can one effectively install `pydantic[email]`? Just adding `email-validator` as an extra dependency doesn't work

Comment:

It seems that it's not enough to install email-validator from conda-forge to emulate what pydantic[email] does. I still get import errors telling me to pip install pydantic[email]. is it possible that pydantic does some extra configuration under the hood depending on whether one installs an extra or not? Generally, I thought that extras just add extra dependencies and doesn't have side effects, but here, it looks like there are side effects.