Re: How to 'ignore' an error in Python?

Unsubscribe On Sat, Apr 29, 2023 at 7:05 PM Chris Angelico wrote: > On Sun, 30 Apr 2023 at 11:58, Chris Green wrote: > > > > Chris Angelico wrote: > > > On Sat, 29 Apr 2023 at 14:27, Kushal Kumaran > wrote: > > > > > > > > On Fri, Apr 28 2023 at 04:55:41 PM, Chris Green wrote: > > > > > I'm

Re: How to 'ignore' an error in Python?

On Sun, 30 Apr 2023 at 12:02, jak wrote: > > Chris Angelico ha scritto: > > Using mkdirs when you only want to make one is inviting problems of > > being subtly wrong, where it creates too many levels of directory. > > Personally, I would just do: > > > Maybe I only say this because it has

Re: How to 'ignore' an error in Python?

Stefan Ram ha scritto: jak writes: Maybe I only say this because it has happened to me too many times but before ignoring the error in the 'except' branch, I would make sure that if the name exists it is a folder and not a file. If the name exists and it is a file's name, this will be

Re: How to 'ignore' an error in Python?

On Sun, 30 Apr 2023 at 11:58, Chris Green wrote: > > Chris Angelico wrote: > > On Sat, 29 Apr 2023 at 14:27, Kushal Kumaran wrote: > > > > > > On Fri, Apr 28 2023 at 04:55:41 PM, Chris Green wrote: > > > > I'm sure I'm missing something obvious here but I can't see an elegant > > > > way to do

Re: How to 'ignore' an error in Python?

Chris Angelico ha scritto: Using mkdirs when you only want to make one is inviting problems of being subtly wrong, where it creates too many levels of directory. Personally, I would just do: Maybe I only say this because it has happened to me too many times but before ignoring the error in

Re: How to 'ignore' an error in Python?

Kushal Kumaran wrote: > On Fri, Apr 28 2023 at 04:55:41 PM, Chris Green wrote: > > I'm sure I'm missing something obvious here but I can't see an elegant > > way to do this. I want to create a directory, but if it exists it's > > not an error and the code should just continue. > > > > So, I

Re: How to 'ignore' an error in Python?

Chris Angelico wrote: > On Sat, 29 Apr 2023 at 14:27, Kushal Kumaran wrote: > > > > On Fri, Apr 28 2023 at 04:55:41 PM, Chris Green wrote: > > > I'm sure I'm missing something obvious here but I can't see an elegant > > > way to do this. I want to create a directory, but if it exists it's > >

Re: How to 'ignore' an error in Python?

On 30/04/23 2:43 am, jak wrote: Maybe I expressed myself badly but I didn't mean to propose alternatives to the EAFP way but just to evaluate the possibility that it is not a folder. If it's not a folder, you'll find out when the next thing you try to do to it fails. You could check for it

RE: How to 'ignore' an error in Python?

require a loss of simplicity. -Original Message- From: Python-list On Behalf Of Kushal Kumaran Sent: Saturday, April 29, 2023 12:19 AM To: python-list@python.org Subject: Re: How to 'ignore' an error in Python? On Fri, Apr 28 2023 at 04:55:41 PM, Chris Green wrote: > I'm sure

Re: How to 'ignore' an error in Python?

On Sat, 29 Apr 2023 at 14:27, Kushal Kumaran wrote: > > On Fri, Apr 28 2023 at 04:55:41 PM, Chris Green wrote: > > I'm sure I'm missing something obvious here but I can't see an elegant > > way to do this. I want to create a directory, but if it exists it's > > not an error and the code should

Re: How to 'ignore' an error in Python?

On Fri, Apr 28 2023 at 04:55:41 PM, Chris Green wrote: > I'm sure I'm missing something obvious here but I can't see an elegant > way to do this. I want to create a directory, but if it exists it's > not an error and the code should just continue. > > So, I have:- > > for dirname in

Re: How to 'ignore' an error in Python?

On 28Apr2023 10:39, Mats Wichmann wrote: For this specific case, you can use os.makedirs: os.makedirs(dirname, exist_ok=True) I'm not a great fan of makedirs because it will make all the missing components, not just the final one. So as an example, if you've got a NAS mounted backup area at

Re: How to 'ignore' an error in Python?

On 28Apr2023 16:55, Chris Green wrote: for dirname in listofdirs: try: os.mkdir(dirname) except FileExistsError: # so what can I do here that says 'carry on regardless' except: # handle any other error, which is really an error #

Re: How to 'ignore' an error in Python?

On 4/28/23 11:05, MRAB wrote: On 2023-04-28 16:55, Chris Green wrote: I'm sure I'm missing something obvious here but I can't see an elegant way to do this.  I want to create a directory, but if it exists it's not an error and the code should just continue. So, I have:- for dirname in

Re: How to 'ignore' an error in Python?

On 2023-04-28 16:55, Chris Green wrote: I'm sure I'm missing something obvious here but I can't see an elegant way to do this. I want to create a directory, but if it exists it's not an error and the code should just continue. So, I have:- for dirname in listofdirs: try:

Re: How to 'ignore' an error in Python?

On 4/28/23 09:55, Chris Green wrote: I'm sure I'm missing something obvious here but I can't see an elegant way to do this. I want to create a directory, but if it exists it's not an error and the code should just continue. So, I have:- for dirname in listofdirs: try:

How to 'ignore' an error in Python?

I'm sure I'm missing something obvious here but I can't see an elegant way to do this. I want to create a directory, but if it exists it's not an error and the code should just continue. So, I have:- for dirname in listofdirs: try: os.mkdir(dirname) except

[issue46061] GCState *gcstate = get_gc_state() gives fatal error in Python 3.10.2

Eric V. Smith added the comment: I understand. Then I'm going to close this issue, since there's nothing we can do. -- resolution: -> rejected stage: -> resolved status: open -> closed ___ Python tracker

[issue46061] GCState *gcstate = get_gc_state() gives fatal error in Python 3.10.2

Ajaya Sutar added the comment: Actually we can not share code due to certain term and conditions. Thanks. -- ___ Python tracker ___

[issue46061] GCState *gcstate = get_gc_state() gives fatal error in Python 3.10.2

Eric V. Smith added the comment: > I was running one python script Again: you need to show us the script that's causing this problem. I (and millions of others) run scripts all the time which do not fail in the way you describe. Unless you show us a script that causes the problem, we cannot

[issue46061] GCState *gcstate = get_gc_state() gives fatal error in Python 3.10.2

-> open title: Journal execution gives fatal error in Python 3.10.1 -> GCState *gcstate = get_gc_state() gives fatal error in Python 3.10.2 ___ Python tracker <htt

[issue31817] Compilation Error with Python 3.6.1/3.6.3 with Tkinter

Change by Irit Katriel : -- stage: -> resolved status: pending -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue31817] Compilation Error with Python 3.6.1/3.6.3 with Tkinter

Irit Katriel added the comment: 3.6 is no longer maintained. Is this a problem on current versions or can be close this? -- nosy: +iritkatriel resolution: -> out of date status: open -> pending ___ Python tracker

[issue46061] Journal execution gives fatal error in Python 3.10.1

Change by Eric V. Smith : -- status: open -> pending ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue46061] Journal execution gives fatal error in Python 3.10.1

Christian Heimes added the comment: We cannot help you unless you show us your code and provide a reproducer. -- nosy: +christian.heimes ___ Python tracker ___

[issue46061] Journal execution gives fatal error in Python 3.10.1

Ajaya Sutar added the comment: It is a simply python script. Even if you will run a simply python script without any content that is giving error. Just for example journal.py if we run it is also giving error. In python 3.8, we are able to create // create sub-interpreter using

[issue46061] Journal execution gives fatal error in Python 3.10.1

Eric V. Smith added the comment: Please show the code that causes this problem. There’s not enough information here to reproduce this failure. -- nosy: +eric.smith ___ Python tracker

[issue46061] Journal execution gives fatal error in Python 3.10.1

execution gives fatal error in Python 3.10.1 type: crash versions: Python 3.10 ___ Python tracker <https://bugs.python.org/issue46061> ___ ___ Python-bugs-list mailing list Unsub

[issue45645] Deep recursion terminates script execution with no error (Windows, Python 3.9)

Eryk Sun added the comment: In theory, a crash could be prevented in most cases by setting a larger stack guarantee (i.e. region of guard pages) via SetThreadStackGuarantee() [1] and using a vectored exception handler [2]. The exception handler can set a flag in the thread state that

[issue45645] Deep recursion terminates script execution with no error (Windows, Python 3.9)

PABLO LOBATO DE LA CRUZ added the comment: I see. Thank you very much Steve :) El vie, 29 oct 2021 a las 0:29, Steve Dower () escribió: > > Steve Dower added the comment: > > > But why does it happen only on Windows? > > Because it's the operating system that is terminating the process :) >

[issue45645] Deep recursion terminates script execution with no error (Windows, Python 3.9)

Steve Dower added the comment: > But why does it happen only on Windows? Because it's the operating system that is terminating the process :) Other operating systems behave differently when you exceed the stack, and may also allocate different amounts of stack space, making it less likely

[issue45645] Deep recursion terminates script execution with no error (Windows, Python 3.9)

PABLO LOBATO DE LA CRUZ added the comment: I see thanks for answering so quickly. But why does it happen only on Windows? El jue, 28 oct 2021 a las 23:09, Steve Dower () escribió: > > Steve Dower added the comment: > > This is almost certainly because of how Windows handles stack overflow >

[issue45645] Deep recursion terminates script execution with no error (Windows, Python 3.9)

Steve Dower added the comment: This is almost certainly because of how Windows handles stack overflow exceptions, and the fact that there's no way for us to detect it reliably. There's some work going on to reduce the C stack depth when calling heavily nested Python code (see issue45256),

[issue45645] Deep recursion terminates script execution with no error (Windows, Python 3.9)

: Deep recursion terminates script execution with no error (Windows, Python 3.9) type: crash versions: Python 3.9 Added file: https://bugs.python.org/file50407/forstack.py ___ Python tracker <https://bugs.python.org/issue45

Re: Request to advise error for python.

Thank you MRAB. As somebody mentioned before, the easiest solution is you can do pip install before typing python. That would work. On Sun, Oct 24, 2021 at 12:00 AM MRAB wrote: > On 2021-10-23 14:53, tommy yama wrote: > > It seems you use windows to install. > > > > > > Then, you need conda.

Re: Request to advise error for python.

On 2021-10-23 14:53, tommy yama wrote: It seems you use windows to install. Then, you need conda. Pip works for Linux. On Windows, 'conda' is for the Anaconda version of Python. If you're using the standard version of Python from python.org you use pip or, preferably, py -m pip. Check

Re: Request to advise error for python.

It seems you use windows to install. Then, you need conda. Pip works for Linux. Check this out. https://numpy.org/install/ On Thu, Oct 21, 2021, 11:35 PM Grant Edwards wrote: > On 2021-10-21, Mats Wichmann wrote: > > > There are some nuances. If you are on a Linux system, Python is a > >

Re: Request to advise error for python.

On 2021-10-21, Mats Wichmann wrote: > There are some nuances. If you are on a Linux system, Python is a > system program and you don't want to try to install into system > locations (you'll run into permission problems anyway), so trying a user > install is useful. So: > > pip install

Re: Request to advise error for python.

On 10/20/21 23:10, 정성학(대학원생-자동차IT융합전공) via Python-list wrote: Hi There are some errors in order to install numpy as follows. pip install numpy File "", line 1 pip install numpy ^ SyntaxError: invalid syntax. Perhaps you forgot a comma? Would you advise me to

Re: Request to advise error for python.

황병희 writes: > Dear 정성학, > [image: image.png] > > If you would like to show us your image, then write down the github/gitlab > link. ... This is example: https://gitlab.com/soyeomul/test/-/commit/80d2b4f5e8eda0238301e9bca5bc33f0127572fd Sincerely, Gopher Byung-Hee --

Re: Request to advise error for python.

Hi There are some errors in order to install numpy as follows. >>> pip install numpy File "", line 1 pip install numpy ^ SyntaxError: invalid syntax. Perhaps you forgot a comma? Would you advise me to correct error and install numpy or pandas? [image: image.png]

Re: Request to advise error for python.

Dear 정성학, >>> [image: image.png] If you would like to show us your image, then write down the github/gitlab link. Of course i assume you have github/gitlab account. Because Mailing server does filter for dangerous things such as image file, video clip, action scripts (computer virus), i think...

Re: Request to advise error for python.

On 10/15/21 5:37 PM, 정성학(대학원생-자동차IT융합전공) via Python-list wrote: > Dear Sir, > > resend request Unfortunately your message is still blank. Attachments such as screenshots are not visible to this list. Whenever you ask questions on the list it is helpful to: - state the operating system you are

Re: Request to advise error for python.

Dear Sir, resend request === Seonghark Jeong KUL(Kookmin Unmanned vehicle research Laboratory) GSAEK, Kookmin Univ. E-Mail: seongh...@kookmin.ac.kr HP: 82-10-3600-7143 === 2021년 10월 16일 (토) 오전 8:08,

[issue33085] *** Error in `python': double free or corruption (out): 0x00007ff5254d50d0 ***

Irit Katriel added the comment: There isn't enough information here for us to do anything about this, and in any case Python 3.6 is no longer maintained. Please create a new issue if you are having this problem with a current version (>= 3.9) and can provide more information about how to

[issue33085] *** Error in `python': double free or corruption (out): 0x00007ff5254d50d0 ***

Change by Irit Katriel : -- components: -2to3 (2.x to 3.x conversion tool) ___ Python tracker ___ ___ Python-bugs-list mailing

Re: "dictionary changed size during iteration" error in Python 3 but not in Python 2

Chris Green wrote: >> >1 - Why doesn't it error in Python 2? >> >> The dict internal implementation has changed. I don't know the >> specifics, but it is now faster and maybe smaller and also now preserves >> insert order. >> > Ah, that probably e

Re: "dictionary changed size during iteration" error in Python 3 but not in Python 2

produces > >the error:- > > > >RuntimeError: dictionary changed size during iteration > > > >I can sort of see why I'm getting the error but have two questions: > > > >1 - Why doesn't it error in Python 2? > > The dict internal implementa

Re: "dictionary changed size during iteration" error in Python 3 but not in Python 2

eError: dictionary changed size during iteration > >I can sort of see why I'm getting the error but have two questions: > >1 - Why doesn't it error in Python 2? The dict internal implementation has changed. I don't know the specifics, but it is now faster and maybe smaller and also no

"dictionary changed size during iteration" error in Python 3 but not in Python 2

of see why I'm getting the error but have two questions: 1 - Why doesn't it error in Python 2? 2 - How do I fix it? Here is the program:- #!/usr/bin/python3 # # # Remove old mail from mbox files # import email import mailbox import os import sys import time # # # Constants/configuration # junkdir

[issue40970] Error in Python Datamodel Documentation

Christopher Yeh added the comment: I understand the two uses of the phrase "built-in": 1) to refer to things included with the Python interpreter (e.g. modules in sys.builtin_module_names, and built-in functions like len() and ord()) 2) to refer to things included with Python that are

[issue40970] Error in Python Datamodel Documentation

Raymond Hettinger added the comment: FWIW, the word "built-in" is being used in two different ways here. It is used in a strict sense for sys.builtin_module_names and in a general sense in the datamodel docs. The former only includes modules compiled into the core exe or dll file. The

[issue40970] Error in Python Datamodel Documentation

Christopher Yeh added the comment: Here's the output from my terminal comparing the `math` standard library module (not always built-in) against the `sys` standard library module (always built-in). On Windows 10 x64, WSL 1, Ubuntu 18.04.02 LTS, Python 3.7.7 installed via conda: math is not

[issue40970] Error in Python Datamodel Documentation

Raymond Hettinger added the comment: What happens when you type, "import math" and "print(type(math))"? -- nosy: +rhettinger ___ Python tracker ___

[issue40970] Error in Python Datamodel Documentation

standard built-in module)" from the documentation. -- assignee: docs@python components: Documentation messages: 371473 nosy: chrisyeh, docs@python priority: normal pull_requests: 20055 severity: normal status: open title: Error in Python Datamodel Documentation type: enhancement vers

[issue31817] Compilation Error with Python 3.6.1/3.6.3 with Tkinter

Ned Deily added the comment: @zhang, Did you try the solution given by dplusplus in the previous message (msg319861)? -- ___ Python tracker ___

[issue31817] Compilation Error with Python 3.6.1/3.6.3 with Tkinter

zhang added the comment: Josh,Did you solve this problem？I met the same error when install python. *** WARNING: renaming "_tkinter" since importing it failed: build/lib.linux-x86_64-3.6/_tkinter.cpython-36m-x86_64-linux-gnu.so: undefined symbol: Tcl_GetCharLength -- no

[issue37025] Misleading error message "Python failed to load the default activation context"

Steve Dower added the comment: Fixed in 2.7 - using issue39553 for removing the code in master. -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker

Re: Error in python installation - was Re: Python, Be Bold!

r from? Python.org or some other distribution like Anaconda? Are you installing for all users, or just for your current user? What has google found about this error message and python? Does google tell you whether anyone else has seen this error message while installing Python before? I don't have Win

Error in python installation

Hello I have Intel DH61 series mother board, with Windows7 64bit + SP1 + some debugging components ( as shown in microsoft website, as service pack for W7) however when I try to install current version of python, it displays error. See the screenshot attached herewith. (board configuration

[issue38745] pygame install error using python 3.8.0

Christian Heimes added the comment: pygame is a third-party component and not developed by the Python core team. This bug tracker is only for issues with Python itself. Please report the problem with pygame. -- nosy: +christian.heimes resolution: -> third party stage: -> resolved

[issue38745] pygame install error using python 3.8.0

ot;, line 302, in ask reply = raw_input( EOFError: EOF when reading a line ERROR: Command errored out with exit status 1: python setup.py egg_info Check the logs for full command output. -- components: Windows

[issue37025] Misleading error message "Python failed to load the default activation context"

Steve Dower added the comment: Merged the 2.7 fix. Let's just delete the whole block in master. -- ___ Python tracker ___ ___

[issue37025] Misleading error message "Python failed to load the default activation context"

Steve Dower added the comment: New changeset 009a6928727b23344613ab6a9a52b9da56ab905c by Steve Dower (Zackery Spytz) in branch '2.7': bpo-37025: AddRefActCtx() shouldn't be checked for failure (GH-16897) https://github.com/python/cpython/commit/009a6928727b23344613ab6a9a52b9da56ab905c

[issue37025] Misleading error message "Python failed to load the default activation context"

Change by Zackery Spytz : -- pull_requests: +16435 pull_request: https://github.com/python/cpython/pull/16897 ___ Python tracker ___

[issue37415] Error build Python with Intel compiler: doesn't provide atomic_uintptr_t

STINNER Victor added the comment: According to Adam J. Stewart, my PR 16717 fix the Python build on ICC: https://github.com/python/cpython/pull/16717#issuecomment-544812182 So I merged it in 3.7, 3.8 and master branches. Adam saw other failures, but it's unrelated issues which should be

[issue37415] Error build Python with Intel compiler: doesn't provide atomic_uintptr_t

miss-islington added the comment: New changeset dbcea39ba713cc5b31fa1a243b16a0128c231c98 by Miss Skeleton (bot) in branch '3.8': bpo-37415: Fix stdatomic.h header check for ICC compiler (GH-16717) https://github.com/python/cpython/commit/dbcea39ba713cc5b31fa1a243b16a0128c231c98 --

[issue37415] Error build Python with Intel compiler: doesn't provide atomic_uintptr_t

miss-islington added the comment: New changeset b102e4f05278c1b06130885eba961bd0193733b4 by Miss Skeleton (bot) in branch '3.7': bpo-37415: Fix stdatomic.h header check for ICC compiler (GH-16717) https://github.com/python/cpython/commit/b102e4f05278c1b06130885eba961bd0193733b4 --

[issue37415] Error build Python with Intel compiler: doesn't provide atomic_uintptr_t

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

[issue37415] Error build Python with Intel compiler: doesn't provide atomic_uintptr_t

STINNER Victor added the comment: New changeset 028f7349a0f6eaea0fec31becb587fcdf6e3cb28 by Victor Stinner in branch 'master': bpo-37415: Fix stdatomic.h header check for ICC compiler (GH-16717) https://github.com/python/cpython/commit/028f7349a0f6eaea0fec31becb587fcdf6e3cb28 --

[issue37415] Error build Python with Intel compiler: doesn't provide atomic_uintptr_t

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

[issue37415] Error build Python with Intel compiler: doesn't provide atomic_uintptr_t

STINNER Victor added the comment: I marked bpo-35473 as duplicate of this issue. -- ___ Python tracker ___ ___ Python-bugs-list

[issue37415] Error build Python with Intel compiler: doesn't provide atomic_uintptr_t

STINNER Victor added the comment: Can someone please test PR 16717 with ICC? -- ___ Python tracker ___ ___ Python-bugs-list

[issue37415] Error build Python with Intel compiler: doesn't provide atomic_uintptr_t

STINNER Victor added the comment: I wrote PR 16717 which uses a similar approach than python.patch. -- components: +Build versions: +Python 3.7, Python 3.8, Python 3.9 ___ Python tracker

[issue37415] Error build Python with Intel compiler: doesn't provide atomic_uintptr_t

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

[issue37025] Misleading error message "Python failed to load the default activation context"

Steve Dower added the comment: This doesn't apply since Python 3.5, as the HAVE_SXS preprocessor variable is not defined. We should just delete this code entirely in 3.9, and patch the message in 2.7. -- versions: -Python 3.7, Python 3.8, Python 3.9

[issue37025] Misleading error message "Python failed to load the default activation context"

Zackery Spytz added the comment: Thank you for the report. I've created a pull request to fix this issue. -- nosy: +ZackerySpytz versions: +Python 2.7, Python 3.8, Python 3.9 ___ Python tracker

[issue37025] Misleading error message "Python failed to load the default activation context"

Change by Zackery Spytz : -- keywords: +patch pull_requests: +16170 stage: -> patch review pull_request: https://github.com/python/cpython/pull/16579 ___ Python tracker ___

[issue37415] Error build Python with Intel compiler: doesn't provide atomic_uintptr_t

Rainer Keller added the comment: We have been experiencing the same problem with compiling Python-3.7.4 on a system with CentOS 7.6 (aka glib-2.17): Intel Compiler 2019.6 implements stdatomic.h. but lacks the definition of atomic_uintptr_t. >From a configure-point of view just failing to

[issue38028] Assertion error in Python 3.8

Ned Deily added the comment: The traceback you provide in the first message: File "/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/pip/_internal/wheel.py", line 324, in move_wheel_files scheme = distutils_scheme( File

[issue38028] Assertion error in Python 3.8

Ana added the comment: Well I have been looking through the interim commands running by the terminal. As far as I can see that’s not Numpy/scipy or whatever. These are the setup tools, wheel and Cython. I may be wrong, but I guess these are pretty universal and are required by many

[issue38028] Assertion error in Python 3.8

Ned Deily added the comment: NumPy has a very complex build and install process including supplying its own modified version of Distutils. You should take up any build and install issues first with the NumPy project and then, if you both agree that there appears to be a problem in Python

[issue38028] Assertion error in Python 3.8

Change by Steve Dower : -- nosy: +Marcus.Smith, dstufft, ncoghlan, paul.moore, pradyunsg ___ Python tracker ___ ___

[issue38028] Assertion error in Python 3.8

all -- components: macOS messages: 351138 nosy: annelischen, ned.deily, ronaldoussoren priority: normal severity: normal status: open title: Assertion error in Python 3.8 type: crash versions: Python 3.8 ___

[issue37415] Error build Python with Intel compiler: doesn't provide atomic_uintptr_t

STINNER Victor added the comment: > Changing Include/pyatomic.h to use _Atomic as suggested by Victor in > msg346785 leads to the error that _Atomic was undefined. No idea how to define a "_Py_atomic_address" type with icc 2019.4 in this case. If someone has a working patch, I can review it

[issue37415] Error build Python with Intel compiler: doesn't provide atomic_uintptr_t

Christian Berger added the comment: I have the same problem on RH6 with icc 2019.4 and Python 3.6.9. Do you want a new bug for that? Changing Include/pyatomic.h to use _Atomic as suggested by Victor in msg346785 leads to the error that _Atomic was undefined. -- nosy: +cberger

[issue37415] Error build Python with Intel compiler: doesn't provide atomic_uintptr_t

Stefan Krah added the comment: Is it available with -std=c11? It is a bit strange that we use -std=c99. I thought that header is C11: https://en.cppreference.com/w/c/atomic -- nosy: +skrah ___ Python tracker

[issue37415] Error build Python with Intel compiler: doesn't provide atomic_uintptr_t

Change by Glenn Johnson : -- nosy: +Glenn Johnson ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue37415] Error build Python with Intel compiler: doesn't provide atomic_uintptr_t

STINNER Victor added the comment: I suggested you to test the following change on the master branch of Python: diff --git a/Include/internal/pycore_atomic.h b/Include/internal/pycore_atomic.h index 336bc3fec2..c624a0cf1c 100644 --- a/Include/internal/pycore_atomic.h +++

[issue37415] Error build Python with Intel compiler: doesn't provide atomic_uintptr_t

Borja added the comment: Two things. I searched a bit more and found "atomic_uint" inside , but it's not exactly the same as what you wrote. What you have put me to try, where do I put it? I attached in case it helps. -- Added file: https://bugs.python.org/file48443/stdatomic.h

[issue37415] Error build Python with Intel compiler: doesn't provide atomic_uintptr_t

ybe you should try: typedef struct _Py_atomic_address { _Atomic Py_uintptr_t _value; } _Py_atomic_address; -- title: Error build Python with Intel compiler -> Error build Python with Intel compiler: doesn't provide atomic_uintptr_t ___ Python t

[issue37415] Error build Python with Intel compiler

Borja added the comment: In pyconfig.h the variable HAVE_STD_ATOMIC appears like this: /* Has stdatomic.h with atomic_int */ #define HAVE_STD_ATOMIC 1 I searched at atomic_uintptr_t and found nothing. -- ___ Python tracker

[issue37415] Error build Python with Intel compiler

STINNER Victor added the comment: atomic_uintptr_t is used if HAVE_STD_ATOMIC defined is defined. Can you please check in pyconfig.h if it's defined? So doesn't provide atomic_uintptr_t with ICC? -- nosy: +vstinner ___ Python tracker

[issue37415] Error build Python with Intel compiler

quot;atomic_uintptr_t" is undefined atomic_uintptr_t _value; ^ compilation aborted for ./Programs/python.c (code 2) -- messages: 346637 nosy: Saszalez priority: normal severity: normal status: open title: Error build Python with Intel compiler type: compile error __

[issue37025] Misleading error message "Python failed to load the default activation context"

atus: open title: Misleading error message "Python failed to load the default activation context" type: behavior versions: Python 3.7 ___ Python tracker <https://bug

Re: Error Opening Python for Windows Download

On 05/12/2019 04:42 PM, Alexandra Mistak wrote: > Hi Python, > > I have unsuccessfully downloaded Python Windows x86-64 executable installer > multiple > times. > > After installation, when I go to launch the program it tells me to

Re: Error Opening Python for Windows Download

Hi, On Mon, May 13, 2019 at 7:50 AM Alexandra Mistak wrote: > > Hi Python, > > I have unsuccessfully downloaded Python Windows x86-64 executable installer > multiple > times. I presume you have Windows 10? > > After installation,

Error Opening Python for Windows Download

Hi Python, I have unsuccessfully downloaded Python Windows x86-64 executable installer multiple times. After installation, when I go to launch the program it tells me to "repair or modify" the app. I click "repair," I try opening

[issue33085] *** Error in `python': double free or corruption (out): 0x00007ff5254d50d0 ***

4.8.5-28)] on linux Type "help", "copyright", "credits" or "license" for more information. >>> *** Error in `python': free(): invalid pointer: 0x7f4eb7a64558 *** === Backtrace: = /lib64/libc.so.6(+0x81499)[0x7f4eb6c45499] pytho

[issue35260] 2to3 Parse Error on Python 3 print() with arguments

Mark Dickinson added the comment: Closing. 2to3 is working as designed here. -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker ___

  1   2   3   4   >