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

[bug] Package inspection doesn't work with python_requires feature in 2.x #13891

Closed
apyvovar opened this issue May 14, 2023 · 2 comments
Closed
Assignees
Milestone

Comments

@apyvovar
Copy link

apyvovar commented May 14, 2023

Environment details

  • Operating System+version: macOS 13.3.1
  • Compiler+version: Apple clang version 14.0.3
  • Conan version: 2.0.4
  • Python version: 3.11.2

Steps to reproduce

  1. Assume, we have the following conanfile.py:
class MyPackage(ConanFile):
    name = "package"
    version = "0.0.1"
    python_requires = "conan_utils/x.x.x"
    python_requires_extend = "conan_utils.MyConanFileTemplate"
  1. Note: the package doesn't have attributes settings, options, description etc. (default attributes are defined in conan_utils).

  2. Calling conan inspect on such package will result in the following output:

    "description": null,
    # ...
    "options": null,
    # ...
    "python_requires": "conan_utils/x.x.x",
    "python_requires_extend": "conan_utils.MyConanFileTemplate",
    # ...
    "settings": null,

I'm aware, that documentation states, that conan inspect ... lists class attributes only, but still, IMO, current issue is a bug, because inspection doesn't represent all package attributes (as in conan 1.x).

@apyvovar apyvovar changed the title [bug] Package inspection doesn't work with python_requires feature [bug] Package inspection doesn't work with python_requires feature in 2.x May 14, 2023
@memsharded memsharded self-assigned this May 14, 2023
@memsharded
Copy link
Member

Hi @apyvovar

Thanks for the report.

I think this has been already improved in #13716, to be released in next 2.0.5 (next week).
If you want to test it from the release/2.0 branch that would be great feedback.

@memsharded memsharded added this to the 2.0.5 milestone May 14, 2023
@memsharded
Copy link
Member

Closing this ticket as solved in 2.0.5 by #13716, but please re-open or create a new ticker for any further question. Thanks!

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

No branches or pull requests

2 participants