Skip to content

Regression: poetry install fails with a build script due to not respecting [build-system] requires #7909

Closed as not planned

Description

@Samreay
  • I am on the latest stable Poetry version, installed using a recommended method.
  • I have searched the issues of this repo and believe that this is not a duplicate.
  • I have consulted the FAQ and blog for any relevant entries or release notes.
  • If an exception occurs when executing a command, I executed it again in debug mode (-vvv option) and have included the output below.

Issue

This issue may be linked to:

This issue might actually be setuptools rather than poetry as well. I'm not sure how the two libraries interact with each other.

We noticed that our latest builds are failing on our poetry install. Our project has cython code, and so part of our build.py that's referenced by the [tool.poetry.build] is to use numpy and cython (which are part of the [build-system].requires section) to compile the cython code into binaries.

Now, a poetry build works as expected, because it installs the build dependencies. But a poetry install on longer works

image
image

To summarise the above images:

  1. numpy is defined in both the [tool.poetry.dependencies] and [build-system].requires
  2. poetry build runs and compiles files successfully
  3. poetry install fails on: Getting requirements to build editable did not run successfully. as poetry/setuptools tries to run our builder.py without dependencies, which fails.

Now the big caveat here, is that I don't know how poetry and setuptools interact, so this might have absolutely nothing to do with poetry and everything to do with setuptools. In which case, please feel free to close out this issue and I'll try to raise it somewhere else.

Has the way to include a build script that has dependencies changed in the latest poetry versions?

Activity

  1. added
    kind/bugSomething isn't working as expected
    status/triageThis issue needs to be triaged
    on May 12, 2023
  2. dimbleby commented on May 12, 2023

    @dimbleby
    Contributor

    not only "linked" to #6154 but surely a straight duplicate

  3. Samreay commented on May 12, 2023

    @Samreay
    Author

    I was unsure if it was a duplicate or not, because I've definitely had poetry building my project after that issue was posted, and its only in the last two months that the build stage we've had has failed. Given the other issue doesn't include the full stack I also wasn't sure if the issue was from the same part of the code. If you like, I can put the screenshots and pyproject.toml over onto that issue, I just didn't want to do so if it might have been a different problem

  4. dimbleby commented on May 12, 2023

    @dimbleby
    Contributor

    you've described the same circumstances, the same actions, and the same symptoms - I think assuming duplicate is sensible.

    By all means add extra information to that issue if you think you have something new to add (though please prefer text to screenshots, so much less annoying to interact with and search)

  5. added
    area/build-systemRelated to PEP 517 packaging (see poetry-core)
    and removed
    status/triageThis issue needs to be triaged
    on Jun 10, 2023
  6. radoering commented on Jun 10, 2023

    @radoering
    Member

    Closing as duplicate of #6154

  7. github-actions commented on Feb 29, 2024

    @github-actions

    This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

  8. locked as resolved and limited conversation to collaborators on Feb 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/build-systemRelated to PEP 517 packaging (see poetry-core)kind/bugSomething isn't working as expectedstatus/duplicateDuplicate issues

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions