pydantic: 1.8.2: pep517 build does not generate DSO modules

Checks

I added a descriptive title to this issue
I have searched (google, github) for similar issues and couldn’t find anything
I have read and followed the docs and still think this is a bug

I’m trying to package your module as an rpm package. So I’m using the typical PEP517 based build, install and test cycle used on building packages from non-root account.

python3 -sBm build -w
install .whl file in </install/prefix>

Looks like on using that procedure DSO mofules are not build.

+ /usr/bin/python3 -sBm build -w
/usr/lib/python3.8/site-packages/setuptools/command/install.py:34: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools.
  warnings.warn(
* Creating virtualenv isolated environment...
* Installing packages in isolated environment... (setuptools >= 40.8.0, wheel)
* Getting dependencies for wheel...
running egg_info
creating pydantic.egg-info
writing manifest file 'pydantic.egg-info/SOURCES.txt'
warning: no previously-included files matching '__pycache__' found anywhere in distribution
warning: no previously-included files matching '*.py[cod]' found anywhere in distribution
writing manifest file 'pydantic.egg-info/SOURCES.txt'
* Installing packages in isolated environment... (wheel)
* Building wheel...
running bdist_wheel
running build
running build_py
creating build
creating build/lib
creating build/lib/pydantic
copying pydantic/__init__.py -> build/lib/pydantic
copying pydantic/_hypothesis_plugin.py -> build/lib/pydantic
copying pydantic/annotated_types.py -> build/lib/pydantic
copying pydantic/class_validators.py -> build/lib/pydantic
copying pydantic/color.py -> build/lib/pydantic
copying pydantic/dataclasses.py -> build/lib/pydantic
copying pydantic/datetime_parse.py -> build/lib/pydantic
copying pydantic/decorator.py -> build/lib/pydantic
copying pydantic/env_settings.py -> build/lib/pydantic
copying pydantic/error_wrappers.py -> build/lib/pydantic
copying pydantic/errors.py -> build/lib/pydantic
copying pydantic/fields.py -> build/lib/pydantic
copying pydantic/generics.py -> build/lib/pydantic
copying pydantic/json.py -> build/lib/pydantic
copying pydantic/main.py -> build/lib/pydantic
copying pydantic/mypy.py -> build/lib/pydantic
copying pydantic/networks.py -> build/lib/pydantic
copying pydantic/parse.py -> build/lib/pydantic
copying pydantic/schema.py -> build/lib/pydantic
copying pydantic/tools.py -> build/lib/pydantic
copying pydantic/types.py -> build/lib/pydantic
copying pydantic/typing.py -> build/lib/pydantic
copying pydantic/utils.py -> build/lib/pydantic
copying pydantic/validators.py -> build/lib/pydantic
copying pydantic/version.py -> build/lib/pydantic
copying pydantic/py.typed -> build/lib/pydantic
running install
running install_lib
creating build/bdist.linux-x86_64
creating build/bdist.linux-x86_64/wheel
creating build/bdist.linux-x86_64/wheel/pydantic
running install_egg_info
running egg_info
warning: no previously-included files matching '__pycache__' found anywhere in distribution
warning: no previously-included files matching '*.py[cod]' found anywhere in distribution
writing manifest file 'pydantic.egg-info/SOURCES.txt'
Copying pydantic.egg-info to build/bdist.linux-x86_64/wheel/pydantic-1.8.2-py3.8.egg-info
running install_scripts
Successfully built pydantic-1.8.2-py3-none-any.whl

About this issue

Original URL
State: closed
Created 3 years ago
Comments: 16 (16 by maintainers)

Most upvoted comments

As for the reported issue:

Cython is present in build env

Cython is not present in the build env because you are invoking build with isolation. Pydantic doesn’t declare Cython as a build dependency (because it doesn’t use pyproject.toml) so build won’t install it.

layday on Dec 26, 2021

I only brought it up because it prevents us from moving completely from setup.cfg to pyproject.toml (as I’ve already said).

Your issue has nothing to do with flake8, but it could relate to us not having a pyproject.toml file.

flake8 has no plans to support pyproject.toml - its author is ideologically opposed to it. It does support .flake8 which is not tied to any other format or build tool, so if you’re looking to move away from setup.cfg, that’d be your best bet.

layday on Dec 26, 2021