[issue16826] Don't check for PYTHONCASEOK if interpreter started with -E

2020-05-14 Thread STINNER Victor
STINNER Victor added the comment: Issue fixed in bpo-38691: commit fc72ab6913f2b5337ae7fda711f2de846d38f479 Author: idomic Date: Mon Mar 9 07:57:53 2020 -0400 bpo-38691: importlib ignores PYTHONCASEOK if -E is used (GH-18627) The importlib module now ignores the PYTHONCASEOK

[issue16826] Don't check for PYTHONCASEOK if interpreter started with -E

2020-01-28 Thread Brett Cannon
Brett Cannon added the comment: This is still occurring. Probably need to add `and sys.ignore_environment` to https://github.com/python/cpython/blob/0cd5bff6b7da3118d0c5a88fc2b80f80eb7c3059/Lib/importlib/_bootstrap_external.py#L38. -- versions: +Python 3.9 -Python 3.6 ___

[issue16826] Don't check for PYTHONCASEOK if interpreter started with -E

2016-09-08 Thread Meador Inge
Meador Inge added the comment: Nothing. I didn't have a Windows box handy to investigate at the time. I do now and can look into this in the next day or so. -- ___ Python tracker

[issue16826] Don't check for PYTHONCASEOK if interpreter started with -E

2016-09-08 Thread Eric Snow
Eric Snow added the comment: What ended up happening with this? -- nosy: +eric.snow versions: +Python 3.6 -Python 3.3, Python 3.4 ___ Python tracker ___ _

[issue16826] Don't check for PYTHONCASEOK if interpreter started with -E

2013-09-04 Thread Meador Inge
Meador Inge added the comment: Reopening to rework test cases. -- resolution: fixed -> stage: committed/rejected -> needs patch status: closed -> open ___ Python tracker ___ ___

[issue16826] Don't check for PYTHONCASEOK if interpreter started with -E

2013-09-03 Thread Roundup Robot
Roundup Robot added the comment: New changeset 7801ef4a4ce3 by Meador Inge in branch '3.3': Issue #16826: Revert fix while Windows issues are being worked out. http://hg.python.org/cpython/rev/7801ef4a4ce3 New changeset a1282b67b4cf by Meador Inge in branch 'default': Issue #16826: Revert fix wh

[issue16826] Don't check for PYTHONCASEOK if interpreter started with -E

2013-09-03 Thread Meador Inge
Meador Inge added the comment: My last commit caused some buildbot failures (http://buildbot.python.org/all/builders/AMD64%20Windows7%20SP1%203.3/builds/1069). I am investigating. -- ___ Python tracker _

[issue16826] Don't check for PYTHONCASEOK if interpreter started with -E

2013-09-03 Thread Meador Inge
Changes by Meador Inge : -- resolution: -> fixed stage: commit review -> committed/rejected status: open -> closed ___ Python tracker ___ ___

[issue16826] Don't check for PYTHONCASEOK if interpreter started with -E

2013-09-03 Thread Roundup Robot
Roundup Robot added the comment: New changeset 934e650abc4d by Meador Inge in branch '3.3': Issue #16826: Don't check for PYTHONCASEOK when using -E. http://hg.python.org/cpython/rev/934e650abc4d New changeset ba850a78cbbc by Meador Inge in branch 'default': Issue #16826: Don't check for PYTHONC

[issue16826] Don't check for PYTHONCASEOK if interpreter started with -E

2013-09-01 Thread Meador Inge
Changes by Meador Inge : -- assignee: -> meador.inge stage: patch review -> commit review ___ Python tracker ___ ___ Python-bugs-list

[issue16826] Don't check for PYTHONCASEOK if interpreter started with -E

2013-04-14 Thread Meador Inge
Meador Inge added the comment: Here is a version which implements the subprocess method for testing suggested by Éric. -- Added file: http://bugs.python.org/file29858/issue16826-1.patch ___ Python tracker _

[issue16826] Don't check for PYTHONCASEOK if interpreter started with -E

2013-01-14 Thread Meador Inge
Meador Inge added the comment: I agree that it is better to cover both cases in one test irrespective of the interpreter command line options. I will take a look at creating a subprocess. Thanks for the review. -- ___ Python tracker

[issue16826] Don't check for PYTHONCASEOK if interpreter started with -E

2013-01-09 Thread Éric Araujo
Éric Araujo added the comment: Code patch looks good, but for tests, I prefer to run subprocesses with the options and output I want, instead of changing the expected results depending on the python-running-tests’ options (and thus, having two tests into one, but always running only one). ---

[issue16826] Don't check for PYTHONCASEOK if interpreter started with -E

2012-12-31 Thread Meador Inge
Meador Inge added the comment: Is the attached OK? -- keywords: +patch nosy: +meador.inge stage: test needed -> patch review Added file: http://bugs.python.org/file28517/issue16826-0.patch ___ Python tracker __

[issue16826] Don't check for PYTHONCASEOK if interpreter started with -E

2012-12-31 Thread Nick Coghlan
Changes by Nick Coghlan : -- nosy: +ncoghlan ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python

[issue16826] Don't check for PYTHONCASEOK if interpreter started with -E

2012-12-31 Thread Brett Cannon
New submission from Brett Cannon: Importlib, when checking for PYTHONCASEOK, does not respect -E as it did in Python 3.2 and earlier (http://hg.python.org/cpython/file/0786dfc3b2b4/Python/import.c#l1933). -- components: Interpreter Core keywords: 3.2regression messages: 178679 nosy: br