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

test.pythoninfo does not print the cross-built sysconfig data #76386

Closed
xdegaye mannequin opened this issue Dec 3, 2017 · 5 comments
Closed

test.pythoninfo does not print the cross-built sysconfig data #76386

xdegaye mannequin opened this issue Dec 3, 2017 · 5 comments
Labels
3.7 build The build process and cross-build type-bug An unexpected behavior, bug, or error

Comments

@xdegaye
Copy link
Mannequin

xdegaye mannequin commented Dec 3, 2017

BPO 32205
Nosy @vstinner, @xdegaye, @moreati
PRs
  • bpo-32205: test.pythoninfo now prints the cross-built sysconfig data #4687
  • Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.

    Show more details

    GitHub fields:

    assignee = None
    closed_at = <Date 2017-12-05.10:52:33.643>
    created_at = <Date 2017-12-03.13:28:10.195>
    labels = ['invalid', 'type-bug', '3.7', 'build']
    title = 'test.pythoninfo does not print the cross-built sysconfig data'
    updated_at = <Date 2017-12-08.16:14:58.015>
    user = 'https://github.com/xdegaye'

    bugs.python.org fields:

    activity = <Date 2017-12-08.16:14:58.015>
    actor = 'xdegaye'
    assignee = 'none'
    closed = True
    closed_date = <Date 2017-12-05.10:52:33.643>
    closer = 'xdegaye'
    components = ['Cross-Build']
    creation = <Date 2017-12-03.13:28:10.195>
    creator = 'xdegaye'
    dependencies = []
    files = []
    hgrepos = []
    issue_num = 32205
    keywords = ['patch']
    message_count = 5.0
    messages = ['307510', '307573', '307578', '307579', '307587']
    nosy_count = 3.0
    nosy_names = ['vstinner', 'xdegaye', 'Alex.Willmer']
    pr_nums = ['4687']
    priority = 'normal'
    resolution = 'not a bug'
    stage = 'resolved'
    status = 'closed'
    superseder = None
    type = 'behavior'
    url = 'https://bugs.python.org/issue32205'
    versions = ['Python 2.7', 'Python 3.6', 'Python 3.7']

    @xdegaye
    Copy link
    Mannequin Author

    xdegaye mannequin commented Dec 3, 2017

    When cross-compiling the only useful information printed by pythoninfo is the cross-built sysconfig data since everything else is related to the native python process used during the cross-build.

    Currently pythoninfo prints the native sysconfig data instead.

    @xdegaye xdegaye mannequin added 3.7 build The build process and cross-build type-bug An unexpected behavior, bug, or error labels Dec 3, 2017
    @vstinner
    Copy link
    Member

    vstinner commented Dec 4, 2017

    I'm not sure of the purpose of this change. You can please elaborate on you use case?

    You use cross-compilation, ok. But why do you want to run test.pythoninfo on the computer building Python, rather than the computer running tests?

    The purpose of test.pythoninfo is to dump informations on tests run by "./python -m test". I wrote it for buildbots.

    If your use case is to have an Android buildbot worker, test.pythoninfo would be run on Android, no?

    @vstinner
    Copy link
    Member

    vstinner commented Dec 4, 2017

    "make pythoninfo" is an alias for ./python -m test.pythoninfo. I added to support Python compiled in shared mode (./configure --enable-shared) and macOS which requires ./python.exe.

    Obviously, for a specific buildbot or specific script, you are free to run directly ./python -m test.pythoninfo, rather than running "make pythoninfo" ;-)

    @vstinner
    Copy link
    Member

    vstinner commented Dec 4, 2017

    See also bpo-32210: Add the versions of the Android SDK and NDK to test.pythoninfo.

    @xdegaye
    Copy link
    Mannequin Author

    xdegaye mannequin commented Dec 4, 2017

    I may have misunderstood the scope of pythoninfo. On Android the readline or sqlite versions are known at build time since they have to be built at that time, but much more useful information can be obtained (or will be obtained) from python running on the device or the emulator.

    For the NDK and SDK versions (bpo-32210), these can be printed by the 'all' target for the NDK and by one of the emulator targets for the SDK.

    This means that both this issue and bpo-32210 may be closed as wont fix.

    @xdegaye xdegaye mannequin closed this as completed Dec 5, 2017
    @xdegaye xdegaye mannequin added the invalid label Dec 8, 2017
    @ezio-melotti ezio-melotti transferred this issue from another repository Apr 10, 2022
    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Labels
    3.7 build The build process and cross-build type-bug An unexpected behavior, bug, or error
    Projects
    None yet
    Development

    No branches or pull requests

    1 participant