You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When explicitly using 0.6.0rc0, I am able to target .pyx files for compilation and they are in fact compiled, but the .pyx files are not copied into the wheel when running hatch build.
I'm working with a very simple test project, so here is the outline:
src/test_cython/
init.py
about.py
example.pyi
example.pyx
__init__.py
from .example import cython_hello
example.pyx
def cython_hello():
print("Hello from Cython!")
On running hatch build two more files are created:
example.c
example.cp312-win_amd64.pyd
The C source file gets copied to the wheel without issue, but the .pyd does not.
Apologies if this is just me not understanding how to use the tool correctly or if I have missed something obvious! As I can get this working in an earlier version (all be it with all .py files getting arbitrarily compiled) I wandered if this could be an actual bug. I can provide the entire Hatch project on request as its only a small set of test code.
The text was updated successfully, but these errors were encountered:
When explicitly using 0.6.0rc0, I am able to target .pyx files for compilation and they are in fact compiled, but the .pyx files are not copied into the wheel when running
hatch build
.I'm working with a very simple test project, so here is the outline:
src/test_cython/
__init__.py
example.pyx
On running
hatch build
two more files are created:The C source file gets copied to the wheel without issue, but the .pyd does not.
Here is the end of the output from
hatch build
:What I think are the relevant parts from pyproject.toml (I'm not using a separate hatch.toml):
Apologies if this is just me not understanding how to use the tool correctly or if I have missed something obvious! As I can get this working in an earlier version (all be it with all .py files getting arbitrarily compiled) I wandered if this could be an actual bug. I can provide the entire Hatch project on request as its only a small set of test code.
The text was updated successfully, but these errors were encountered: