Skip to content

Use specs instead of just __loader__ in C code #86298

Description

@brettcannon
BPO 42132
Nosy @brettcannon, @corona10

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 = None
created_at = <Date 2020-10-23.22:16:01.448>
labels = ['interpreter-core', 'type-bug', '3.10']
title = 'Use specs instead of just __loader__ in C code'
updated_at = <Date 2020-10-24.16:28:23.690>
user = 'https://github.com/brettcannon'

bugs.python.org fields:

activity = <Date 2020-10-24.16:28:23.690>
actor = 'corona10'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2020-10-23.22:16:01.448>
creator = 'brett.cannon'
dependencies = []
files = []
hgrepos = []
issue_num = 42132
keywords = []
message_count = 1.0
messages = ['379483']
nosy_count = 2.0
nosy_names = ['brett.cannon', 'corona10']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue42132'
versions = ['Python 3.10']

Linked PRs

Activity

  1. brettcannon commented on Oct 23, 2020

    @brettcannon
    MemberAuthor

    _warnings.c, pylifecycle.c, and pythonrun.c all either use or set __loader__ but without also falling back on __spec__.

  2. transferred this issue fromon Apr 10, 2022
  3. warsaw commented on Oct 3, 2022

    @warsaw
    Member

    I'm going to take a look at these module attribute issues during the 2022 core sprint.

  4. moved this to Todo in Sprinton Oct 3, 2022
  5. warsaw commented on Oct 4, 2022

    @warsaw
    Member

    I have _warnings.c implemented and tested.

  6. warsaw commented on Oct 4, 2022

    @warsaw
    Member

    I think there's nothing to do for pythonrun.c. These set __loader__ but not __spec__ directly, and the documentation outlines the expected semantics. If the documented semantics are incorrect, then there should be a separate tracking bug for that case.

    Looking at pylifecycle.c next.

  7. 7 remaining items

  8. added 2 commits that reference this issue on Jul 24, 2024
  9. serhiy-storchaka commented on Jul 25, 2024

    @serhiy-storchaka
    Member

    These warnings are only emitted for the C implementation. See #122255.

  10. added a commit that references this issue on Jul 25, 2024
  11. added a commit that references this issue on Jul 25, 2024
  12. added 3 commits that reference this issue on Jul 25, 2024
  13. added a commit that references this issue on Aug 8, 2024
  14. added 2 commits that reference this issue on Aug 8, 2024
  15. added a commit that references this issue on Aug 9, 2024
  16. added a commit that references this issue on Aug 14, 2024
  17. added a commit that references this issue on Aug 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Projects

    • Status
      Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions