[issue44076] issue with list in Python 3.8.5

Mohamed added the comment: Thanks a lot -- ___ Python tracker <https://bugs.python.org/issue44076> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue44076] issue with list in Python 3.8.5

Mohamed added the comment: These are the latest updates: May 08, 2021, Microsoft Edge May 06, 2021, Microsoft OneDrive May 01, 2021, Update Health Tools There is no an option to uninstall the following: May 01, 2021-KB4023057: Update for Windows 10 Update Service components

[issue44076] issue with list in Python 3.8.5

Mohamed added the comment: I chose Python to develop a huge information system. I completed about 47%, and made a demonstration, so everything was working correctly, as evidenced by presence of the data Now, I can't go back, and I can't mo

[issue44076] issue with list in Python 3.8.5

Mohamed added the comment: This statement in the main program which is calling a subprogram, to control for multiple runs. Even I close this statement, the issue is same. del sys.modules['cm_asset_add'] I've contacted Microsoft support team, they have different opin

[issue44076] issue with list in Python 3.8.5

Mohamed added the comment: Please find attached, the demo with dummy data. As I mentioned, it was working fine until May 1st. Also, As I mentioned, in case I call MasterApp at the end of add function data appears correctly. This means a malfunction occurred after Windows Update, and it

[issue44076] issue with list in Python 3.8.5

Mohamed added the comment: I made changes but result is same: xrec = self.treedata.selection()[0] xrec = int(xrec[1:], 16) - 1 print('xrec: ', xrec) itemXid = assetinfo_lst[xrec] itemXid = itemXid[1] Exception in Tkinter callback Traceback (most r

[issue44076] issue with list in Python 3.8.5

Mohamed added the comment: I tried the following method: class MasterApp(object): def __init__(self, root): def fun_astinfo_add(self): ... assetinfo_lst.append(lst_values) ... MasterApp(root) ... if

[issue44076] issue with list in Python 3.8.5

Mohamed added the comment: I'm using tkinter for a long time, my application was running fine till 1st May, and suddenly happen this issue. After adding a new data to a list, it showing in some places of tkinter components. For example, in treeview, it shows based on running sp

[issue44076] issue with list in Python 3.8.5

Mohamed added the comment: I'm using tkinter 8.6 with Python -- ___ Python tracker <https://bugs.python.org/issue44076> ___ ___ Python-bugs-list m

[issue44076] issue with list in Python 3.8.5

New submission from Mohamed : I am using Python under Windows 10 on Dell for a log time. All of my applications on Python were working fine. Suddenly from the beginning of May, My apps do not update a "list" data after a new insert, even with small data volume. As well as choosin

[issue43971] documentation: no spacing around default args in annotated function

Change by Mohamed Moselhy : -- keywords: +patch pull_requests: +24393 stage: -> patch review pull_request: https://github.com/python/cpython/pull/25702 ___ Python tracker <https://bugs.python.org/issu

[issue43971] documentation: no spacing around default args in annotated function

New submission from Mohamed Moselhy : See https://www.python.org/dev/peps/pep-0008/#function-annotations The first section of https://docs.python.org/3/library/dataclasses.html shows quantity_on_hand: int=0, when there should be spacing around the '=' according to PEP 8 (see

[issue42694] Failed test_new_curses_panel in test_curses

Change by mohamed koubaa : -- nosy: +koubaa nosy_count: 2.0 -> 3.0 pull_requests: +22797 pull_request: https://github.com/python/cpython/pull/21986 ___ Python tracker <https://bugs.python.org/issu

[issue1635741] Py_Finalize() doesn't clear all Python objects at exit

Change by mohamed koubaa : -- pull_requests: +22417 pull_request: https://github.com/python/cpython/pull/23535 ___ Python tracker <https://bugs.python.org/issue1635

[issue1635741] Py_Finalize() doesn't clear all Python objects at exit

Change by mohamed koubaa : -- pull_requests: +22195 pull_request: https://github.com/python/cpython/pull/23304 ___ Python tracker <https://bugs.python.org/issue1635

[issue1635741] Py_Finalize() doesn't clear all Python objects at exit

Change by mohamed koubaa : -- pull_requests: +22092 pull_request: https://github.com/python/cpython/pull/23188 ___ Python tracker <https://bugs.python.org/issue1635

[issue1635741] Py_Finalize() doesn't clear all Python objects at exit

Change by mohamed koubaa : -- pull_requests: +22091 pull_request: https://github.com/python/cpython/pull/23139 ___ Python tracker <https://bugs.python.org/issue1635

[issue1635741] Py_Finalize() doesn't clear all Python objects at exit

Change by mohamed koubaa : -- pull_requests: +22007 pull_request: https://github.com/python/cpython/pull/23091 ___ Python tracker <https://bugs.python.org/issue1635

[issue1635741] Py_Finalize() doesn't clear all Python objects at exit

Change by mohamed koubaa : -- pull_requests: +21507 pull_request: https://github.com/python/cpython/pull/22490 ___ Python tracker <https://bugs.python.org/issue1635

[issue1635741] Py_Finalize() doesn't clear all Python objects at exit

Change by mohamed koubaa : -- pull_requests: +21506 pull_request: https://github.com/python/cpython/pull/22489 ___ Python tracker <https://bugs.python.org/issue1635

[issue1635741] Py_Finalize() doesn't clear all Python objects at exit

Change by mohamed koubaa : -- pull_requests: +21372 pull_request: https://github.com/python/cpython/pull/22328 ___ Python tracker <https://bugs.python.org/issue1635

[issue41790] C-API documentation

New submission from mohamed koubaa : The C-API documentation introduction contains an error: "Almost all Python objects live on the heap: you never declare an automatic or static variable of type :c:type:`PyObject`, only pointer variables of type :c:type:`PyObject*` can be declared. The

[issue1635741] Py_Finalize() doesn't clear all Python objects at exit

Change by mohamed koubaa : -- pull_requests: +21297 pull_request: https://github.com/python/cpython/pull/22242 ___ Python tracker <https://bugs.python.org/issue1635

[issue1635741] Py_Finalize() doesn't clear all Python objects at exit

Change by mohamed koubaa : -- pull_requests: +21296 pull_request: https://github.com/python/cpython/pull/22240 ___ Python tracker <https://bugs.python.org/issue1635

[issue1635741] Py_Finalize() doesn't clear all Python objects at exit

Change by mohamed koubaa : -- pull_requests: +21277 pull_request: https://github.com/python/cpython/pull/2 ___ Python tracker <https://bugs.python.org/issue1635

[issue1635741] Py_Finalize() doesn't clear all Python objects at exit

Change by mohamed koubaa : -- pull_requests: +21275 pull_request: https://github.com/python/cpython/pull/0 ___ Python tracker <https://bugs.python.org/issue1635

[issue40600] Add option to disallow > 1 instance of an extension module

mohamed koubaa added the comment: Something like this? ``` static PyObject *def; PyMODINIT_FUNC PyInit_mymod(void) { if (def == NULL) { def = PyModuleDef_Init(&mymod); } return def; } ``` Then add a flag to PyModuleDef to indicate it is already

[issue1635741] Py_Finalize() doesn't clear all Python objects at exit

Change by mohamed koubaa : -- pull_requests: +21239 pull_request: https://github.com/python/cpython/pull/22165 ___ Python tracker <https://bugs.python.org/issue1635

[issue1635741] Py_Finalize() doesn't clear all Python objects at exit

Change by mohamed koubaa : -- pull_requests: +21238 pull_request: https://github.com/python/cpython/pull/22164 ___ Python tracker <https://bugs.python.org/issue1635

[issue1635741] Py_Finalize() doesn't clear all Python objects at exit

Change by mohamed koubaa : -- pull_requests: +21227 pull_request: https://github.com/python/cpython/pull/22145 ___ Python tracker <https://bugs.python.org/issue1635

[issue40600] Add option to disallow > 1 instance of an extension module

mohamed koubaa added the comment: What about a new PyModuleDef_Slot function? ``` static int my_can_create(/*need any arg??, InterpreterState, etc?*/) { if (test_global_condition()) { return -1; //Don't allow creation } return 0; //Allow creation }; s

[issue1635741] Py_Finalize() doesn't clear all Python objects at exit

Change by mohamed koubaa : -- pull_requests: +21223 pull_request: https://github.com/python/cpython/pull/22139 ___ Python tracker <https://bugs.python.org/issue1635

[issue36533] logging regression with threading + fork are mixed in 3.7.1rc2 (deadlock potential)

Change by mohamed koubaa : -- nosy: +koubaa nosy_count: 7.0 -> 8.0 pull_requests: +21219 pull_request: https://github.com/python/cpython/pull/21986 ___ Python tracker <https://bugs.python.org/issu

[issue33802] Regression in logging configuration

Change by mohamed koubaa : -- nosy: +koubaa nosy_count: 7.0 -> 8.0 pull_requests: +21220 pull_request: https://github.com/python/cpython/pull/21986 ___ Python tracker <https://bugs.python.org/issu

[issue6721] Locks in the standard library should be sanitized on fork

Change by mohamed koubaa : -- nosy: +koubaa nosy_count: 27.0 -> 28.0 pull_requests: +21218 pull_request: https://github.com/python/cpython/pull/21986 ___ Python tracker <https://bugs.python.org/iss

[issue1635741] Py_Finalize() doesn't clear all Python objects at exit

Change by mohamed koubaa : -- pull_requests: +21216 pull_request: https://github.com/python/cpython/pull/22134 ___ Python tracker <https://bugs.python.org/issue1635

[issue1635741] Py_Finalize() doesn't clear all Python objects at exit

Change by mohamed koubaa : -- pull_requests: +21212 pull_request: https://github.com/python/cpython/pull/22131 ___ Python tracker <https://bugs.python.org/issue1635

[issue41713] _signal module leak: test_interpreters leaked [1424, 1422, 1424] references

mohamed koubaa added the comment: Sounds like there needs to be some python-wide global state that perhaps the signal module wraps rather than owns. I could try to prototype it if you agree -- nosy: +koubaa ___ Python tracker <ht

[issue1635741] Py_Finalize() doesn't clear all Python objects at exit

Change by mohamed koubaa : -- pull_requests: +21148 pull_request: https://github.com/python/cpython/pull/22051 ___ Python tracker <https://bugs.python.org/issue1635

[issue1635741] Py_Finalize() doesn't clear all Python objects at exit

Change by mohamed koubaa : -- pull_requests: +21147 pull_request: https://github.com/python/cpython/pull/22050 ___ Python tracker <https://bugs.python.org/issue1635

[issue1635741] Py_Finalize() doesn't clear all Python objects at exit

Change by mohamed koubaa : -- pull_requests: +21146 pull_request: https://github.com/python/cpython/pull/22049 ___ Python tracker <https://bugs.python.org/issue1635

[issue1635741] Py_Finalize() doesn't clear all Python objects at exit

Change by mohamed koubaa : -- pull_requests: +21109 pull_request: https://github.com/python/cpython/pull/22003 ___ Python tracker <https://bugs.python.org/issue1635

[issue1635741] Py_Finalize() doesn't clear all Python objects at exit

Change by mohamed koubaa : -- pull_requests: +21101 pull_request: https://github.com/python/cpython/pull/21995 ___ Python tracker <https://bugs.python.org/issue1635

[issue1635741] Py_Finalize() doesn't clear all Python objects at exit

Change by mohamed koubaa : -- pull_requests: +21095 pull_request: https://github.com/python/cpython/pull/21986 ___ Python tracker <https://bugs.python.org/issue1635

[issue1635741] Py_Finalize() doesn't clear all Python objects at exit

Change by mohamed koubaa : -- pull_requests: +21094 pull_request: https://github.com/python/cpython/pull/21985 ___ Python tracker <https://bugs.python.org/issue1635

[issue1635741] Py_Finalize() doesn't clear all Python objects at exit

Change by mohamed koubaa : -- pull_requests: +20982 pull_request: https://github.com/python/cpython/pull/21855 ___ Python tracker <https://bugs.python.org/issue1635

[issue1635741] Py_Finalize() doesn't clear all Python objects at exit

Change by mohamed koubaa : -- pull_requests: +20983 pull_request: https://github.com/python/cpython/pull/21856 ___ Python tracker <https://bugs.python.org/issue1635

[issue1635741] Py_Finalize() doesn't clear all Python objects at exit

Change by mohamed koubaa : -- pull_requests: +20949 pull_request: https://github.com/python/cpython/pull/21818 ___ Python tracker <https://bugs.python.org/issue1635

[issue1635741] Py_Finalize() doesn't clear all Python objects at exit

Change by mohamed koubaa : -- pull_requests: +20567 pull_request: https://github.com/python/cpython/pull/21418 ___ Python tracker <https://bugs.python.org/issue1635

[issue1635741] Py_Finalize() doesn't clear all Python objects at exit

Change by mohamed koubaa : -- pull_requests: +20522 pull_request: https://github.com/python/cpython/pull/21378 ___ Python tracker <https://bugs.python.org/issue1635

[issue1635741] Py_Finalize() doesn't clear all Python objects at exit

Change by mohamed koubaa : -- pull_requests: +20521 pull_request: https://github.com/python/cpython/pull/21375 ___ Python tracker <https://bugs.python.org/issue1635

[issue1635741] Py_Finalize() doesn't clear all Python objects at exit

Change by mohamed koubaa : -- pull_requests: +20519 pull_request: https://github.com/python/cpython/pull/21371 ___ Python tracker <https://bugs.python.org/issue1635

[issue1635741] Py_Finalize() doesn't clear all Python objects at exit

Change by mohamed koubaa : -- nosy: +koubaa nosy_count: 16.0 -> 17.0 pull_requests: +20471 pull_request: https://github.com/python/cpython/pull/21319 ___ Python tracker <https://bugs.python.org/issue1

[issue23542] Update PEP 476 for using urllib2.build_opener()

Shakeel Mohamed added the comment: Hi, any plans to do this? If not, we can close it. -- ___ Python tracker <http://bugs.python.org/issue23542> ___ ___ Python-bug

[issue23542] Update PEP 476 for using urllib2.build_opener()

New submission from Shakeel Mohamed: In the "Opting Out" section of PEP 476, there's a workaround for disabling SSL cert verification. I think it would be worth updating the section to include the following workaround when using urllib2.build_opener(), like so: unverif