Include configuration overrides the package format constraints.

[e0lithic]

• [x] I am on the latest Poetry version.

• [x] I have searched the issues of this repo and believe that this is not a duplicate.

• [x] If an exception occurs when executing a command, I executed it again in debug mode (-vvv option).

• OS version and name: Ubuntu 20.04

• Poetry version: 1.05

  Project Structure

  . ├── LICENSE.rst ├── noxfile.py ├── poetry.lock ├── pyproject.toml ├── README.rst ├── src │ ├── mypkg │ └── mypkgobfuscated └── tests ├── __init_\.py └── test_main.py

pyproject.toml

[tool.poetry]
name = "mypkg"
version = "0.1.0"
description = "Mypkg"
authors = ["tester <info@tester.com>"]
license = "MIT"
readme = "README.rst"
homepage = "xyz"
repository = "xyz"
documentation = "https://xyz.readthedocs.io"

include = ["src/mypkg_obfuscated/**/*"]

packages = [
    {include = "mypkg", from = "src", format = "sdist"},
    {include = "mypkg_obfuscated", from = "src", format="wheel"},
]

[build-system]
requires = ["poetry>=0.12"]
build-backend = "poetry.masonry.api"

PS: .gitignore contains the mypkg_obfuscated file as this is generated by running obfuscation and security scripts on mypkg. Hence there was a specific need to us the include in pyproject.toml even though mypkg_obfuscated was already present in the packages.

Usecase

• Complete development is being done on mypkg hence we want it to be included into the packages for testing using pytest, nox and other utilities.
• mypkg_obfuscated is being added to the packages because we only want to send the obfuscated version of the package when distributing
• The format option has been included to ensure that we include only the obfuscated version of the code in the wheel format which will be shipped.

Issue

It appears that include overrides the package formats and the mypkg_obfuscated gets included in the sdist format as well overriding the format constraints of the packages. I also went through the documentation but there isn't a format specific include/exclude which I came across.

I am very new to poetry and it could very well be the case that this is the intended flow for the include construct. Additionally if it appears that I am using poetry in unintended way , please feel free to guide me on the best method to achieve the specified goal of being able to distribute only the obfuscated code(mypkg_obfuscated) and be able to run all development flows on the open code(mypkg) in the same project.

And finally a vote of thanks for the great project. :+1:

[e0lithic]

@finswimmer In your opinion am I using poetry in the optimal way or there are other better ways of achieving the above ?

[finswimmer]

@e0lithic I think I understood what you are trying to do, and on the first look, your way looks like the correct way. But I have to investigate a little bit more whether the current behavior is a bug or a feature ;)

[e0lithic]

Hi again, considering there's been quite some time. I hope everyone is doing well. @finswimmer or @sdispater . Do you still consider the above mentioned issue as being a bug or an intended feature? I would plan building the scripts around poetry accordingly.