[issue44264] Add descriptive error message when environment variable not detected

Irit Katriel added the comment: > os.environ defines the __delitem__ method to call C unsetenv(). Thus `del > os.environ[varname]` does unset the environment variable, at least at the > level of the C runtime. For the current process, yes. But it's not that what the user ne

[issue44264] Add descriptive error message when environment variable not detected

Eryk Sun added the comment: This is just a point of clarification. > my del did not change the environment variable os.environ defines the __delitem__ method to call C unsetenv(). Thus `del os.environ[varname]` does unset the environment variable, at least at the level of the C runt

[issue44264] Add descriptive error message when environment variable not detected

Irit Katriel added the comment: I vote to reject this proposal. Unless another core dev disagrees, I will close this issue. -- status: pending -> open ___ Python tracker ___

[issue44264] Add descriptive error message when environment variable not detected

Irit Katriel added the comment: > if a user of a Python program were to come across it, it may not indicate > what they needed to do to avoid the crash. The user of a program should not see this exception. The program should translate it to an error that would make sense to the user.

[issue44264] Add descriptive error message when environment variable not detected

Irit Katriel added the comment: It's not necessarily true that the environment variable is not set just because the key is not in os.environ. In this example my del did not change the environment variable: >>> import os >>> os.environ['TMPDIR'

[issue46226] User specific paths added to System PATH environment variable

Steve Dower added the comment: Without logs or the ability to reproduce it, there's not much we can do. I ran the install and it put the variables in the right place, so it's not happening all the time. The install logs are usually detailed enough to see why decisions like this are made,

[issue46226] User specific paths added to System PATH environment variable

Aleksandr Krymskiy added the comment: I installed 3.10, and then removed 3.9 that I had installed previously. Python is installed in "C:\Program Files\Python310". The only thing that exists under %LocalAppData% is an empty directory

[issue46226] User specific paths added to System PATH environment variable

Eryk Sun added the comment: Were you upgrading an existing installation of Python 3.10? Did it actually install in "C:\Program Files\Python310"? Is Python currently installed in per-user "%LocalAppData%\Programs\Python\Python310"? Was it ever installed there? -- nosy: +eryksun

[issue46226] User specific paths added to System PATH environment variable

Aleksandr Krymskiy added the comment: I did not find install logs in my user %TEMP% or C:\Windows\Temp. I did select "install for all users" during setup just like I always do, but I did not override the default location of "C:\Program Files\Python310". I attached screenshots of the options

[issue46226] User specific paths added to System PATH environment variable

Steve Dower added the comment: If you have them, can you share your install logs (look in %TEMP% for files starting with "Python"). If not, please share your install options. By default, this works fine. You have to make some specific modifications to the install options to do what you've

[issue46226] User specific paths added to System PATH environment variable

Change by Ned Deily : -- components: +Windows nosy: +paul.moore, steve.dower, tim.golden, zach.ware ___ Python tracker ___ ___

[issue46226] User specific paths added to System PATH environment variable

environment variable and only global (C:\Program Files\Python310\...) kept in the System scope by the installer. Please see my screenshot - the highlighted should be moved to User scoped PATH var. -- components: Installation files: py_paths.png messages: 409507 nosy: akrymskiy priority: normal

[issue45969] When uninstalling Python under Windows the "Scripts" folders should be removed from the PATH environment variable

Steve Dower added the comment: Unless someone can find an authoring bug under Tools/msi, I don't think we can do anything about this. We rely on the built-in Windows support for adding and removing these variables, and if that's broken, we can't do anything with our current setup. I really

[issue45969] When uninstalling Python under Windows the "Scripts" folders should be removed from the PATH environment variable

New submission from Luca : This issue is related to: https://bugs.python.org/issue3561 and: https://bugs.python.org/issue45968 When installing Python under Windows, if the "Add Python 3.x to PATH" option is flagged, the following two folders are added to the PATH environmen

[issue45968] Windows installer should add also "%USERPROFILE%\AppData\Roaming\Python\Python3x\Scripts" folder to the PATH environment variable

New submission from Luca : This issue is related to https://bugs.python.org/issue3561 When installing Python under Windows, if the "Add Python 3.x to PATH" option is flagged, the following two folders are added to the PATH environment variable: %USERPROFILE%\AppData\Local\Progr

[issue43773] macOS official installer builds not respecting DYLD_LIBRARY_PATH environment variable.

Change by Brandt Bucher : -- nosy: -brandtbucher ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue43773] macOS official installer builds not respecting DYLD_LIBRARY_PATH environment variable.

Change by Brandt Bucher : -- pull_requests: -27755 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue43773] macOS official installer builds not respecting DYLD_LIBRARY_PATH environment variable.

Change by Brandt Bucher : -- nosy: +brandtbucher nosy_count: 3.0 -> 4.0 pull_requests: +27755 pull_request: https://github.com/python/cpython/pull/29505 ___ Python tracker ___

[issue44352] Native Windows Python builds running on Europe/Moscow TZ report wrong time from datetime.datetime.now when there is TZ environment variable also set to Europe/Moscow

Mike Kaganski added the comment: @Eryk Sun: yes, of course you are right - but please see the date of the commit; I didn't know what you kindly explained me in your reply yesterday :-) Thank you again. -- ___ Python tracker

[issue44352] Native Windows Python builds running on Europe/Moscow TZ report wrong time from datetime.datetime.now when there is TZ environment variable also set to Europe/Moscow

Eryk Sun added the comment: Note that this explanation in your commit is wrong and unhelpful: "likely because datetime.datetime.now in the native Windows Python takes into account both system timezone data and the TZ environment variable". When TZ is set, localtime() is based only

[issue44352] Native Windows Python builds running on Europe/Moscow TZ report wrong time from datetime.datetime.now when there is TZ environment variable also set to Europe/Moscow

Mike Kaganski added the comment: Thank you Eryk! This is a good workaround for me. I have implemented it: https://git.libreoffice.org/core/+/3bcaa4ba79477a21251ddaa06e0ea159196a7ffb It looks like it's not a Python's problem; I suppose this may be closed. Thanks again! --

[issue44352] Native Windows Python builds running on Europe/Moscow TZ report wrong time from datetime.datetime.now when there is TZ environment variable also set to Europe/Moscow

Eryk Sun added the comment: > 2. Execute 'set TZ=Europe/Moscow' The Windows C runtime supports a simple format for the TZ environment variable, which is detailed in the documentation of _tzset() [1]. For example, it's "MSK-3" for Moscow Standard Time. It's -3 because the o

[issue44352] Native Windows Python builds running on Europe/Moscow TZ report wrong time from datetime.datetime.now when there is TZ environment variable also set to Europe/Moscow

Change by Zachary Ware : -- nosy: +belopolsky, p-ganssle ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue44352] Native Windows Python builds running on Europe/Moscow TZ report wrong time from datetime.datetime.now when there is TZ environment variable also set to Europe/Moscow

. > datetime.datetime(2021, 6, 8, 19, 59, 21, 925240) instead of proper > datetime.datetime(2021, 6, 8, 21, 59, 21, 925240) which appears when step #2 is skipped. Possibly Python takes both system time zone information *and* the environment variable into account when calculating the time. I suppose it

[issue44264] Add descriptive error message when environment variable not detected

New submission from David Gene : Using os.environ[KEY] with a non-existent environment variable key only gives a simple KeyError, which may be fine for a developer to understand, but if a user of a Python program were to come across it, it may not indicate what they needed to do to avoid

[issue43773] macOS official installer builds not respecting DYLD_LIBRARY_PATH environment variable.

Carlton Gibson added the comment: Hi Ned, Thank you for the reply. That explains a lot. I hadn't considered that SQLite would be statically linked. > I believe the original reason was to avoid linking with the Apple-supplied > system copy of the sqlite3 library. I can see that being a

[issue43773] macOS official installer builds not respecting DYLD_LIBRARY_PATH environment variable.

Ned Deily added the comment: Thanks for the report. However, I think you've drawn the wrong conclusion form what you've observed. The reason you are unable to do what you are trying to do is that the _sqlite3 module included with the python.org macOS Pythons is statically linked with its

[issue43773] macOS official installer builds not respecting DYLD_LIBRARY_PATH environment variable.

New submission from Carlton Gibson : Hi. On MacOS 11.3 "Big Sur", with the latest 3.9.4 installed with the official installer downloaded from python.org, the DYLD_LIBRARY_PATH environment variable is not being respected. This looks very similar to Issue40198 https://bugs.

[issue27263] Tkinter sets the HOME environment variable, breaking scripts

Eryk Sun added the comment: ntpath.expanduser() no longer uses HOME (though the doc string still refers to $HOME), so at least that problem is resolved. I suppose IDLE could work around the HOME issue in Windows by passing env=os.environ.copy() in the subprocess.Popen() call that creates

[issue37680] distutils appends LDFLAGS environment variable before object file names

Steve Dower added the comment: Distutils is now deprecated (see PEP 632) and all tagged issues are being closed. From now until removal, only release blocking issues will be considered for distutils. If this issue does not relate to distutils, please remove the component and reopen it. If

[issue28288] Expose environment variable PYTHON_OPT as alternative to command line options

Irit Katriel added the comment: It's too late for the PYTHON3WARNINGS variable in 2.7, but Serhiy's suggestion for PYTHON_OPTS can still be implemented. Updating title and version accordingly. -- nosy: +iritkatriel title: Expose environment variable for Py_Py3kWarningFlag -> Exp

[issue35328] Set a environment variable for venv prompt

Change by Brett Cannon : -- resolution: fixed -> status: closed -> open versions: +Python 3.10 -Python 3.9 ___ Python tracker ___

[issue35328] Set a environment variable for venv prompt

Change by Mathias Fredriksson : -- pull_requests: +21368 pull_request: https://github.com/python/cpython/pull/22324 ___ Python tracker ___

[issue35328] Set a environment variable for venv prompt

Mathias Fredriksson added the comment: I believe GH-21587 does not fully address this issue because VIRTUAL_ENV_PROMPT is being conditionally set only if VIRTUAL_ENV_DISABLE_PROMPT is unset. Shell prompts must set VIRTUAL_ENV_DISABLE_PROMPT to non-empty to prevent venv from hijacking PS1.

[issue35328] Set a environment variable for venv prompt

Change by Vinay Sajip : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ ___

[issue35328] Set a environment variable for venv prompt

Vinay Sajip added the comment: New changeset c82dda1e08c4b74ca24f88d6a549d93108c319cf by Zackery Spytz in branch 'master': bpo-35328: Set VIRTUAL_ENV_PROMPT at venv activation (GH-21587) https://github.com/python/cpython/commit/c82dda1e08c4b74ca24f88d6a549d93108c319cf --

[issue35328] Set a environment variable for venv prompt

Change by Zackery Spytz : -- nosy: +ZackerySpytz nosy_count: 6.0 -> 7.0 pull_requests: +20727 pull_request: https://github.com/python/cpython/pull/21587 ___ Python tracker ___

[issue40886] Add PYTHONLOGGING environment variable and -L cmdline argument

Change by Karthikeyan Singaravelan : -- nosy: +vinay.sajip ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue40886] Add PYTHONLOGGING environment variable and -L cmdline argument

New submission from Bar Harel : Per discussion on mailing list, I suggest adding a PYTHONLOGGING environment variable, and a matching -L cmdline argument. When set to a logging level of choice, they will initiate basicConfig with the appropriate level. For example, "py.exe -L

[issue30462] urllib does not support NO_PROXY environment variable containing domain with asterisk

Cheryl Sabella added the comment: The original pull request has been closed for inactivity, so this is now available for anyone to work on. Please credit the original author if anyone change is based on the original PR. Thanks! -- nosy: +cheryl.sabella versions: +Python 3.10

[issue40781] Remove sys._debugmallocstats() function and PYTHONMALLOCSTATS environment variable

STINNER Victor added the comment: > Please, don't remove these as I use them often to track down memory usage in > a similar way as Inada-san. Ok, sure. I close my issue and I closed my PR. Note: Maybe your advanced usage of statistics on memory allocators should be documented somewhere in

[issue40781] Remove sys._debugmallocstats() function and PYTHONMALLOCSTATS environment variable

Pablo Galindo Salgado added the comment: Please, don't remove these as I use them often to track down memory usage in a similar way as Inada-san. -- ___ Python tracker ___

[issue40781] Remove sys._debugmallocstats() function and PYTHONMALLOCSTATS environment variable

Inada Naoki added the comment: I use it often when I investigate memory usage. It provides some useful information even in release Python build. For example: * Which size class is most allocated? * How many block are allocated? * Which size class have most free blocks? (e.g. Inner

[issue40781] Remove sys._debugmallocstats() function and PYTHONMALLOCSTATS environment variable

STINNER Victor added the comment: > I use it often when I investigate memory usage. Oh. If you use it, we should keep the feature :-) -- ___ Python tracker ___

[issue40781] Remove sys._debugmallocstats() function and PYTHONMALLOCSTATS environment variable

New submission from STINNER Victor : I never used sys._debugmallocstats() function or PYTHONMALLOCSTATS environment variable, whereas I spend significant time on optimizing memory allocators and free lists. The output is written into stderr which is very convenient to process these data. I

[issue40781] Remove sys._debugmallocstats() function and PYTHONMALLOCSTATS environment variable

STINNER Victor added the comment: "Recent" changes in builtin Python debug tools. * In Python 3.9, I removed the "COUNT_ALLOCS" special build: bpo-39489. * Debug build of Python 3.8 is now ABI compatible with release build: I disabled Py_TRACE_REFS macro by default in --with-pydebug build.

[issue40781] Remove sys._debugmallocstats() function and PYTHONMALLOCSTATS environment variable

STINNER Victor added the comment: INADA-san, Antoine, Serhiy, Pablo: did any of you used this feature recently? Is it useful for your hacks? -- nosy: +inada.naoki, pablogsal, pitrou, serhiy.storchaka ___ Python tracker

[issue40781] Remove sys._debugmallocstats() function and PYTHONMALLOCSTATS environment variable

Change by STINNER Victor : -- keywords: +patch pull_requests: +19687 stage: -> patch review pull_request: https://github.com/python/cpython/pull/20430 ___ Python tracker ___

[issue40542] path environment variable not created correctly

Zachary Ware added the comment: Just a note to add my full support for what Steve said. PATH is frequently abused on Windows, and we only have the option at all because people become unreasonably upset if it's not there. I wouldn't be against adding a "you don't actually want this, use

[issue40542] path environment variable not created correctly

Steve Dower added the comment: Yes, it is bad behaviour, but it is very upsetting for many people to not have the option. This is why it's disabled by default, and why I regularly discourage people from selecting the option (and quite often get abused for taking the trouble... oh well...

[issue40542] path environment variable not created correctly

is from RtlGetExePath (undocumented). This is similar to the result from RtlGetSearchPath, except, instead of supporting a safe search mode, RtlGetExePath allows excluding the current directory (%__CD__%) from the search path by setting the environment variable NoDefaultCurrentDirectoryInExePath

[issue40542] path environment variable not created correctly

Change by Ned Deily : -- components: +Windows nosy: +paul.moore, steve.dower, tim.golden, zach.ware ___ Python tracker ___ ___

[issue40542] path environment variable not created correctly

New submission from Roman : The Python 3.8 for Windows installer has an option to add the install folder to the path environment variable. It adds the path to the front of the list so that it is the first item. According to my understanding, this is bad behavior. It should add new path items

[issue39395] The os module should unset() environment variable at exit

Eric Snow added the comment: FTR, #39376 is related (avoid the process-global env vars in the first place). -- nosy: +eric.snow ___ Python tracker ___

[issue39395] The os module should unset() environment variable at exit

STINNER Victor added the comment: On non-Windows platforms, Python now requires setenv() and unsetenv() functions to build. setenv() and unsetenv() should be available on all platforms supported by Python. If it's not the case, someone can maintain a downstream patch which is a revert of

[issue39395] The os module should unset() environment variable at exit

Change by STINNER Victor : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue39395] The os module should unset() environment variable at exit

STINNER Victor added the comment: New changeset b8d1262e8afe7b907b4a394a191739571092acdb by Victor Stinner in branch 'master': bpo-39395: putenv() and unsetenv() always available (GH-18135) https://github.com/python/cpython/commit/b8d1262e8afe7b907b4a394a191739571092acdb --

[issue39395] The os module should unset() environment variable at exit

STINNER Victor added the comment: Clearing environment variables at exit has a drawback: it changes the behavior in code executed after Python finalization (Py_FinalizeEx() call). It may cause regression. So I proposed PR 18135 to fix this issue differently: on non-Windows platforms,

[issue39395] The os module should unset() environment variable at exit

Change by STINNER Victor : -- pull_requests: +17521 pull_request: https://github.com/python/cpython/pull/18135 ___ Python tracker ___

[issue39395] The os module should unset() environment variable at exit

STINNER Victor added the comment: I closed bpo-39406: os.putenv() is now implemented with setenv() if available. The internal putenv_dict is no longer used on Windows and if setenv() is available. Now only non-Windows platforms without setenv() are affected by this issue. --

[issue39395] The os module should unset() environment variable at exit

STINNER Victor added the comment: > Issue39406 is a new feature. In any case we should fix potential crash in > older Python versions. Python 3.8 and older are not affected by this issue since they never destroy the posix_putenv_garbage dictionary: memory is never released. --

[issue39395] The os module should unset() environment variable at exit

Change by STINNER Victor : -- versions: -Python 3.7, Python 3.8 ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue39395] The os module should unset() environment variable at exit

Serhiy Storchaka added the comment: Issue39406 is a new feature. In any case we should fix potential crash in older Python versions. -- nosy: +serhiy.storchaka ___ Python tracker

[issue39395] The os module should unset() environment variable at exit

Change by Serhiy Storchaka : -- type: -> crash versions: +Python 3.7, Python 3.8 ___ Python tracker ___ ___ Python-bugs-list

[issue39395] The os module should unset() environment variable at exit

STINNER Victor added the comment: I proposed bpo-39406 which avoids to have to clear environment variables set by Python at exit on platforms providing setenv(). -- ___ Python tracker

[issue39395] The os module should unset() environment variable at exit

STINNER Victor added the comment: Fedora downstream issue, crash in the "elements" package: https://bugzilla.redhat.com/show_bug.cgi?id=1791761 -- ___ Python tracker ___

[issue39395] The os module should unset() environment variable at exit

Change by STINNER Victor : -- keywords: +patch pull_requests: +17471 stage: -> patch review pull_request: https://github.com/python/cpython/pull/18078 ___ Python tracker ___

[issue39395] The os module should unset() environment variable at exit

59a347b9007be8d2. The _posix_clear() function is now called by _PyImport_Cleanup(). Problem: the glibc is not aware that Python is exiting and that the memory of the environment variable has been released. Next access to environment variables ("environ" C variable, putenv, setenv, uns

[issue39122] Environment variable PYTHONUSERBASE is not set during customized Python Installation

New submission from Sara Martínez Giner : Environment variable PYTHONUSERBASE is not set during customized Python Installation. Python installer 3.7.6(x64) / Windows 10 Check 1: Customize the installation to install Python in C:\Python37 for all users. Result: Access Denied using pip

[issue35328] Set a environment variable for venv prompt

Change by Vinay Sajip : -- versions: +Python 3.9 -Python 3.8 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34709] Suggestion: make getpass.getuser() also look at SUDO_USER environment variable

closed title: Suggestion: make getuser.getpass() also look at SUDO_USER environment variable -> Suggestion: make getpass.getuser() also look at SUDO_USER environment variable ___ Python tracker <https://bugs.pyt

[issue34709] Suggestion: make getuser.getpass() also look at SUDO_USER environment variable

Zachary Ware added the comment: I agree with Steven in that I'm not quite sure this is a good change, but I also see that it would be useful in some cases. Perhaps either a `check_sudo_user=False` keyword-only parameter, or a `vars_to_check=()` parameter would be better? Adding Gregory P.

[issue37680] distutils appends LDFLAGS environment variable before object file names

Change by Batuhan : -- nosy: +BTaskaya ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue37680] distutils appends LDFLAGS environment variable before object file names

Omer Ozarslan added the comment: Attached a better example. Run make (static_example|shared_example|working_shared_example). -- Added file: https://bugs.python.org/file48506/python-issue-2.tar.gz ___ Python tracker

[issue37680] distutils appends LDFLAGS environment variable before object file names

New submission from Omer Ozarslan : distutils honors some environment variables during extension build, however, LDFLAGS is appended before declaring object files. This causes undefined symbols during importing an extension built with some static libraries using this environment variable

[issue37411] testEnviron (test.test_wsgiref.HandlerTests) fails when environment variable X is set

Change by STINNER Victor : -- pull_requests: -14383 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue37411] testEnviron (test.test_wsgiref.HandlerTests) fails when environment variable X is set

Change by hai shi : -- pull_requests: +14383 pull_request: https://github.com/python/cpython/pull/14453 ___ Python tracker ___ ___

[issue37411] testEnviron (test.test_wsgiref.HandlerTests) fails when environment variable X is set

Change by STINNER Victor : -- pull_requests: -14375 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue37411] testEnviron (test.test_wsgiref.HandlerTests) fails when environment variable X is set

Change by hai shi : -- pull_requests: +14375 pull_request: https://github.com/python/cpython/pull/14453 ___ Python tracker ___ ___

[issue37411] testEnviron (test.test_wsgiref.HandlerTests) fails when environment variable X is set

Change by Karthikeyan Singaravelan : -- pull_requests: -14269 ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue37411] testEnviron (test.test_wsgiref.HandlerTests) fails when environment variable X is set

Change by hai shi : -- pull_requests: +14269 pull_request: https://github.com/python/cpython/pull/14453 ___ Python tracker ___ ___

[issue37411] testEnviron (test.test_wsgiref.HandlerTests) fails when environment variable X is set

STINNER Victor added the comment: Ok, the bug is now fixed in 2.7, 3.7, 3.8 and master branches. Thanks Miro for the report. I also enhanced the test to test all variables of handler.environ. -- resolution: -> fixed stage: patch review -> resolved status: open -> closed

[issue37411] testEnviron (test.test_wsgiref.HandlerTests) fails when environment variable X is set

STINNER Victor added the comment: New changeset dfa9499ccbc14a4227ca8d0c1728e2beacbb45c6 by Victor Stinner (Miss Islington (bot)) in branch '2.7': [2.7] bpo-37411: Rewrite test_wsgiref.testEnviron() (GH-14394) (GH-14404)

[issue37411] testEnviron (test.test_wsgiref.HandlerTests) fails when environment variable X is set

miss-islington added the comment: New changeset bdbd5e895ddf9aefcb79cdc52341f0697ad6aea0 by Miss Islington (bot) in branch '3.8': bpo-37411: Rewrite test_wsgiref.testEnviron() (GH-14394) https://github.com/python/cpython/commit/bdbd5e895ddf9aefcb79cdc52341f0697ad6aea0 --

[issue37411] testEnviron (test.test_wsgiref.HandlerTests) fails when environment variable X is set

miss-islington added the comment: New changeset 814c7aefc2b8e9892bce3d59c0ab39563d658aa2 by Miss Islington (bot) in branch '3.7': bpo-37411: Rewrite test_wsgiref.testEnviron() (GH-14394) https://github.com/python/cpython/commit/814c7aefc2b8e9892bce3d59c0ab39563d658aa2 -- nosy:

[issue37411] testEnviron (test.test_wsgiref.HandlerTests) fails when environment variable X is set

Change by miss-islington : -- pull_requests: +14216 pull_request: https://github.com/python/cpython/pull/14404 ___ Python tracker ___

[issue37411] testEnviron (test.test_wsgiref.HandlerTests) fails when environment variable X is set

Change by miss-islington : -- pull_requests: +14215 pull_request: https://github.com/python/cpython/pull/14403 ___ Python tracker ___

[issue37411] testEnviron (test.test_wsgiref.HandlerTests) fails when environment variable X is set

Change by miss-islington : -- pull_requests: +14214 pull_request: https://github.com/python/cpython/pull/14402 ___ Python tracker ___

[issue37411] testEnviron (test.test_wsgiref.HandlerTests) fails when environment variable X is set

STINNER Victor added the comment: New changeset 5150d327924959639215ed0a78feffc0d88258da by Victor Stinner in branch 'master': bpo-37411: Rewrite test_wsgiref.testEnviron() (GH-14394) https://github.com/python/cpython/commit/5150d327924959639215ed0a78feffc0d88258da --

[issue37411] testEnviron (test.test_wsgiref.HandlerTests) fails when environment variable X is set

Change by STINNER Victor : -- versions: +Python 2.7 -Python 3.6 ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue37411] testEnviron (test.test_wsgiref.HandlerTests) fails when environment variable X is set

STINNER Victor added the comment: I wrote PR 14394 to fix the test. -- ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue37411] testEnviron (test.test_wsgiref.HandlerTests) fails when environment variable X is set

Change by STINNER Victor : -- keywords: +patch pull_requests: +14208 stage: -> patch review pull_request: https://github.com/python/cpython/pull/14394 ___ Python tracker ___

[issue37411] testEnviron (test.test_wsgiref.HandlerTests) fails when environment variable X is set

Change by Karthikeyan Singaravelan : -- nosy: +xtreak ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue37411] testEnviron (test.test_wsgiref.HandlerTests) fails when environment variable X is set

New submission from Miro Hrončok : In Fedora CI, we use the environment variable X to set tests to skip: https://src.fedoraproject.org/tests/python/blob/bd3ec9505cd37d80fe47fbb8234928abcfc0c658/f/selftest/parallel.sh#_9 - lines 9 and 21 However, I'Ve realized that testEnviron

[issue29779] New environment variable PYTHONHISTORY

Zackery Spytz added the comment: PR 473 was closed by its author. I have created a new pull request (PR 13208) that addresses all of Berker Peksag's comments on the old PR. Please have a look. -- nosy: +ZackerySpytz versions: +Python 3.8 -Python 3.7

[issue35328] Set a environment variable for venv prompt

Brett Cannon added the comment: You can open a new PR with co-author or basing off of their fork if it's still around. -- ___ Python tracker ___

[issue35328] Set a environment variable for venv prompt

Lysandros Nikolaou added the comment: @brettcannon, yeah I saw that, but there hasn't been any progress since November. I'm still interested in this though. What would the correct workflow be? Pushing commits to the same PR or opening a new one with a co-author? --

[issue35328] Set a environment variable for venv prompt

Brett Cannon added the comment: @lys.nikolaou it looks like there was an initial PR, but it only updated things for Bash and not for all the other shells that we support for virtual environments. -- nosy: +brett.cannon ___ Python tracker

[issue35328] Set a environment variable for venv prompt

Lysandros Nikolaou added the comment: Is anybody still working on this? -- ___ Python tracker ___ ___ Python-bugs-list mailing

[issue35328] Set a environment variable for venv prompt

Change by Lysandros Nikolaou : -- nosy: +lys.nikolaou ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

  1   2   3   4   5   6   7   >