Skip to content

Windows installer missing free-threading library #119679

Closed

Description

@da-woods

Bug report

Bug description:

Tested with Python 3.13b1 release.

I've been trying to help someone test a simple extension module with the free-threading interpreter on Windows, which ultimately failed because it was missing python313t.lib so was unable to link.

image

image

Installed libraries:

image

CPython versions tested on:

3.13

Operating systems tested on:

Windows

Linked PRs

Activity

  1. zooba commented on May 28, 2024

    @zooba
    Member

    That's actually a shockingly short list of libs in there... do you have log files handy? They'll be under %TEMP%\Python*.log, and the main one I'm interested in will end with dev (and probably be the latest date, in case you have multiple installs).

  2. da-woods commented on May 28, 2024

    @da-woods
    ContributorAuthor

    Python 3.13.0b1 (64-bit)_20240528190955_004_dev_JustForMe.log

    Here. Can provide other logs as needed.

    I only have one install of 3.13 - I uninstalled and started from scratch for the sake of this issue.

  3. zooba commented on May 28, 2024

    @zooba
    Member

    Huh, no, it just looks like we've only ever shipped that few. I guess I'm so used to working with the Nuget packages that I had forgotten the MSI is more selective.

    We should add the free-threaded libs to the old installer. We should also reduce the libs included in the other packages to avoid shipping too many files.

  4. self-assigned this
    on May 28, 2024
  5. added
    3.13only security fixes
    3.14bugs and security fixes
    on May 28, 2024
  6. added 2 commits that reference this issue on May 30, 2024
  7. added a commit that references this issue on Jun 3, 2024
  8. added a commit that references this issue on Jun 3, 2024
  9. added a commit that references this issue on Jun 3, 2024
  10. added a commit that references this issue on Jun 5, 2024
  11. added 2 commits that reference this issue on Jun 5, 2024
  12. added a commit that references this issue on Jun 6, 2024
  13. added a commit that references this issue on Jun 6, 2024
  14. stonebig commented on Jun 8, 2024

    @stonebig

    I'm afraid to discover it didn't make it to b2.... by any luck am I wrong ?

  15. zooba commented on Jun 10, 2024

    @zooba
    Member

    It should be fixed in b2 - the later fix is for scripts that aren't part of the release, so shouldn't make a difference.

    If you're doing a clean install and not seeing the files, please grab your log files and attach those as well.

  16. added 2 commits that reference this issue on Jul 11, 2024
  17. added 2 commits that reference this issue on Jul 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions