Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support tracing? poetry2nix is hard to debug #1730

Open
heimalne opened this issue Jul 12, 2024 · 0 comments
Open

Support tracing? poetry2nix is hard to debug #1730

heimalne opened this issue Jul 12, 2024 · 0 comments

Comments

@heimalne
Copy link

heimalne commented Jul 12, 2024

Just wanted to suggest that poetry2nix could benefit from some refactoring and supporting some form of tracing to debug issues by answering at least the following questions:

  • what packages were found in poetry.lock and considered
  • which packages matched for the current machine (and architecture)
  • which packages from poetry.lock were not considered for current machine and why
  • which packages were used in the end after all hacks and overrides were applied.

Maybe someone with more intricate knowledge of the code base would be able to work on this?

Related issues that would benefit from having this:
#1616
#1729
#1519
#1340
NixOS/nixpkgs#229210
#1597
etc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant