[BUG]: pyd file is created without suffix and along new dlls

[polortiz4]

Required prerequisites

• Make sure you've read the documentation. Your issue may be addressed there.
• Search the issue tracker and Discussions to verify that this hasn't already been reported. +1 or comment there if it has.
• Consider asking first in the Gitter chat room or in a Discussion.

What version (or hash if on master) of pybind11 are you using?

2.10.3

Problem description

When building my module, I expect the output to be a PYD file such as pybind11_example.cp310-win_amd64.pyd.
Instead, the output I get is pybind11_example (without an extension name) along with additional files python310.dll and zlib1.dll. Manually adding the extension name and (optionally) deleting the additional .dll appear to give a functioning output, but I believe this is not the intended behavior.
This was not the case in version 2.9.1, where the behavior is as expected.

I believe I saw a report of a problem like this one earlier, but can't seem to find it anymore, so I apologize if I'm duplicating a post.

I have a large project and am trying to turn it into a minimum reproducible example, but here it goes, using Python3.10 and pybind11 installed via vcpkg. The structure is inspired from this blog article https://www.benjack.io/hybrid-python/c-packages-revisited/.

pybind11_example.zip

Reproducible example code

No response

Is this a regression? Put the last known working version here if it is.

2.9.1

[henryiii]

This is pretty heavily tested (https://github.com/pybind/scikit_build_example, https://github.com/pybind/cmake_example, https://github.com/pybind/python_example, and various places in scikit-build(also core & examples), so would be surprised if it's broken. When I try your example on my mac, it works fine:

$ virtualenv .venv
$ .venv/bin/pip install .
$ ls .venv/lib/python3.11/site-packages/pybind11_example
pybind11_example.cpython-311-darwin.so*

PS: I'd not recommend a 5+ year old article asking you to use things like distutils.LooseVersion - something like scikit-build-core and pyproject.toml would be a lot better. See https://github.com/pybind/scikit_build_example for a more modern approach, or https://github.com/pybind/cmake_example for a more correct version of that manual setuptools approach.

[polortiz4]

I also tried it in my mac and it worked. I failed to mention this happens in Windows. I tried it on another Windows machine and it also worked.. So I apologize for not giving a truly reproducible code, I'll explore what difference there is between the two Windows devices I've tried this on for a more comprehensive report.

As far as the PS, fair point.. But switching to scikit-build and pyproject.toml has given me more headaches [1, 2] than it has resolved.

[henryiii]

I'd go with scikit_build_core. And for now, I'd completely ignore editable installs with any method; they are just not supported for binaries in manual hacks on setuptools, scikit-build, or scikit-build-core (but core will be gaining support soon!). If you are using an old version of setuptools, it used to work sort of; adding pyproject.toml will give you the latest setuptools generally.

Also, conda is not an environment you can easily build things in. It's only an environment for pre-built binaries built with Conda-build, not pip - they have their own compiler stack, for example. If you really want to use it for development of binary builds, you can install the compilers package from conda-forge, which might help. But officially, you have to set up a Conda-build recipe (ideally on CI systems like conda-forge) to build properly.

[polortiz4]

Ok, upon further examination I've noticed this behavior occurs with the pybind11 installed via vcpkg. When installing pybind11 via conda install -c conda-forge pybind11==2.10.3, the package is built as expected, but if I set CMAKE_TOOLCHAIN_FILE to <vcpkg-root>\scripts\buildsystems\vcpkg.cmake (and having installed pybind11 2.10.3 via vcpkg install pybind11), I observe the behavior above: both in Mac and Windows.
I am unsure if this means my issue should be brought up in the vcpkg github repository or if this remains the appropriate thread for it. Please advice and thank you for your help.