Skip to content

Conversation

@ncoghlan
Copy link
Contributor

@ncoghlan ncoghlan commented Oct 24, 2017

The startup refactoring means command line settings
are now applied after settings are read from the
environment.

This updates the way command line settings are applied
to account for that, ensures more settings are first read
from the environment in _PyInitializeCore, and adds a
simple test case covering the flags that are easy to check.

https://bugs.python.org/issue31845

The startup refactoring means command line settings
are now applied after settings are read from the
environment.

This updates the way command line settings are applied
to account for that, ensures more settings are first read
from the environment in _PyInitializeCore, and adds a
simple test case covering the flags that are easy to check.
@ncoghlan
Copy link
Contributor Author

@zooba Could you have a look over this and see if any of the newer Windows settings are affected? I don't think they are, since they're envvar only, and this was a problem with envvar vs cmdline settings, but it doesn't hurt to double check.

Copy link
Member

@zooba zooba left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like it's fine.

@ncoghlan ncoghlan merged commit d7ac061 into python:master Oct 25, 2017
@ncoghlan ncoghlan deleted the issue-31845-envvar-based-config-tests branch March 30, 2018 07:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants