Skip to content

Broken verbose/debug logging for poetry build with a custom build script #8756

@vit-zikmund

Description

@vit-zikmund
  • Poetry version: 1.7.1

  • Python version: 3.11

  • OS version and name: Fedora 38

  • pyproject.toml:

    hidden here
    [tool.poetry]
    name = "poetry-custom-build"
    version = "0.1.0"
    
    [tool.poetry.dependencies]
    python = "^3.10"
    
    [tool.poetry.build]
    script = "build.py"  # there's nothing in it
    
    [build-system]
    requires = ["poetry-core>=1.0.0", 'tomli; python_version < "3.11"']
    build-backend = "poetry.core.masonry.api"
  • 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

I'm not getting any debug -vvv logs from the poetry build command when using a custom build script with additional dependencies. The wheel builder source code obviously has some logger.debug() calls, but they're not getting through.

Note, I was able to pinpoint the root cause. PR is on its way.

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/bugSomething isn't working as expected

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions