Multiple top-level packages discovered in a flat-layout

[orientnab]

On installation pip throws:

error: Multiple top-level packages discovered in a flat-layout

It seems it can be fixed by specifying the package in setup.py.

setup(
    ...,
    packages=["gymnasium_playground_gridworld"],
)

[jgvictores]

Hi!

I know the solution you propose is very easy to incorporate, but I'm curious given the context:

• python setup.py check only asks for url and either (author and author_email) or (maintainer and maintainer_email)
• https://packaging.python.org/en/latest/guides/distributing-packages-using-setuptools/#packages says that although the packages can be listed manually, setuptools.find_packages() finds them automatically.
• No mention of the packages field in https://setuptools.pypa.io/en/latest/userguide/quickstart.html#basic-use (setup.py tab)
• I may be wrong on this one, but I do not see any "Multiple top-level packages" :sweat_smile:

Quite a bit of blame on setuptools found via https://www.google.com/search?q=Multiple+top-level+packages+discovered+in+a+flat-layout.

1. Which version are you using (pip list | grep setuptools)?
2. Could you try with a more recent version?

Cheers!

[orientnab]

It seems something has become stricter or more explicit since 61.0. I'm on 65.5, I don't think a new version will change much.

Please note that it is not possible to automatically derive a single name when the distribution consists of multiple top-level packages or modules. (https://setuptools.pypa.io/en/latest/history.html#v61-0-0)

_Users that don’t set packages, pymodules, or configuration are still likely to observe the auto-discovery behavior, which may halt the build if the project contains multiple directories and/or multiple Python files directly under the project root. (https://setuptools.pypa.io/en/latest/history.html#v61-1-0)

[jgvictores]

Ok, thanks for the info!

I've committed directly to master at https://github.com/roboticslab-uc3m/gymnasium-playground/commit/31ba44d436f16de5e849bee400efd9d63cbdfdea

Please reopen if this did not make the fix!