fix(nx-python): handle "from" for packages in pyproject.toml during the build process

[ap0nia]

Current Behavior

The build breaks when I depend on a local package with a src directory.

Expected Behavior

If I correctly specify from="src" in the local package's pyproject.toml, the build should succeed. When using a typical flat package structure, it works fine. i.e. like this

../lib
├── pyproject.toml
└── awesome_package/
    └── __init__.py

More Details

I have a package: my_package. A snippet of its pyproject.toml is here:

[tool.poetry.dependencies.awsome_package]
path = "../lib"
develop = true

The local package that's being referred to has a directory structure like this.

../lib
├── pyproject.toml
└── src/
     └── awesome_package/
        └── __init__.py

The local package also has this snippet in its pyproject.toml

[[tool.poetry.packages]]
include = "awesome_package"
from = "src"

I think it would be correct behavior for the build process, i.e. nx build my_package to find the awesome_package from the ../lib/src directory.

Miscellaneous

src vs. flat layout details

[lucasvieirasilva]

Hey @ap0nia many thanks for the contribution, really appreciate that.
The CI is failing because it's missing code coverage for your changes, could add a test case to the build executor when the from is provided?

Here's an example: https://github.com/lucasvieirasilva/nx-plugins/blob/main/packages/nx-python/src/executors/build/executor.spec.ts#L702-L883

Thanks again!

[ap0nia]

I copied the test case you referenced and removed some of the stuff that didn't need to be tested again. Let me know if you'd like me to trim it down anymore, or anything!

[github-actions]

🎉 This PR is included in version 16.3.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀