-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
0.9.24: create temporary directory before build trashes pep517 build #81
Comments
Hi! Thanks for the bug report. I'm not yet able to reproduce what you're seeing (trying with python3.10 and python3.12 on a Mac, haven't tried a linux machine, which is probably required). Do you have any idea where the SPECPARTS directory is coming from? Is it maybe present before you try running I've never heard of this directory before, but it looks like it might come from Can you try adding
to the pyproject.toml file and see if that fixes the problem? I think it probably will, and while I don't think it should be needed (i.e., I'm guessing that rpm is messing things up), I wouldn't object to adding it. |
This issue has nothing to do wit OS platform. |
Okay. With that I can reproduce the problem. I suppose asking you to not create a top-level directory and then run this command is not helpful? :) At any rate, can you try the fix I'm suggesting above (with the change to pyproject.toml)? It fixes the problem for me and I believe it is probably the right way to address this sort of thing. |
FYI: many jaraco modules are suffering the same issue as they mowed recently to simplest possible pyprojest.toml. |
This is now fixed in version 0.9.25. |
Tested and works now 👍 |
You're welcome! Thanks again for reporting the bug. |
Looks like some bits are missing in pyproject.toml and create temporary directory in source tree before start build trashes pep517 build.
In this case has been created
SPECPARTS/
direcotry as part of the packaging process.The text was updated successfully, but these errors were encountered: