Skip to content

-X frozen_modules not defaulting to "off" on Windows when running in source tree? #89814

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

Closed
ericsnowcurrently opened this issue Oct 28, 2021 · 6 comments
Labels
3.11 only security fixes interpreter-core (Objects, Python, Grammar, and Parser dirs) type-bug An unexpected behavior, bug, or error

Comments

@ericsnowcurrently
Copy link
Member

BPO 45651
Nosy @gvanrossum, @ericsnowcurrently, @FFY00

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 2021-10-28.17:09:35.792>
labels = ['interpreter-core', 'type-bug', '3.11']
title = '-X frozen_modules not defaulting to "off" on Windows when running in source tree?'
updated_at = <Date 2021-11-04.16:04:32.727>
user = 'https://github.com/ericsnowcurrently'

bugs.python.org fields:

activity = <Date 2021-11-04.16:04:32.727>
actor = 'gvanrossum'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2021-10-28.17:09:35.792>
creator = 'eric.snow'
dependencies = []
files = []
hgrepos = []
issue_num = 45651
keywords = []
message_count = 3.0
messages = ['405201', '405730', '405732']
nosy_count = 3.0
nosy_names = ['gvanrossum', 'eric.snow', 'FFY00']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue45651'
versions = ['Python 3.11']

@ericsnowcurrently
Copy link
Member Author

(forked from https://bugs.python.org/issue45020#msg404344)

On Mon, Oct 18, 2021 at 7:14 PM Guido van Rossum <[email protected]> wrote:

I built on Windows with default options (PCbuild\build.bat) and it looks like the frozen modules are used by default even though I am running in the source directory. (I put a printf() call in unmarshal_frozen_code().)

We need to verify if this is still the case. First we need to make sure there's a test that checks the default (both when running out of the source tree and when not). I suspect the case Guido observed hasn't been fixed yet.

@ericsnowcurrently ericsnowcurrently added 3.11 only security fixes interpreter-core (Objects, Python, Grammar, and Parser dirs) type-bug An unexpected behavior, bug, or error labels Oct 28, 2021
@ericsnowcurrently ericsnowcurrently changed the title -X frozen_modules not defaulting to "on" on Windows? -X frozen_modules not defaulting to "off" on Windows when running in source tree? Oct 28, 2021
@ericsnowcurrently ericsnowcurrently changed the title -X frozen_modules not defaulting to "on" on Windows? -X frozen_modules not defaulting to "off" on Windows when running in source tree? Oct 28, 2021
@ericsnowcurrently
Copy link
Member Author

maybe related: #29041 (comment)

@gvanrossum
Copy link
Member

Yes, that’s definitely the problem.

@ezio-melotti ezio-melotti transferred this issue from another repository Apr 10, 2022
@kumaraditya303
Copy link
Contributor

@gvanrossum Can you verify if this issue still exists after #91173 ?

@gvanrossum
Copy link
Member

Verified on Mac that in a debug build from source in the repo, os is not frozen. 👍

@kumaraditya303
Copy link
Contributor

kumaraditya303 commented May 4, 2022

Great! that all known issue were fixed before beta.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3.11 only security fixes interpreter-core (Objects, Python, Grammar, and Parser dirs) type-bug An unexpected behavior, bug, or error
Projects
None yet
Development

No branches or pull requests

3 participants