[issue7946] Convoy effect with I/O bound threads and New GIL

2022-03-21 Thread Sophist


Sophist  added the comment:

> https://docs.google.com/document/d/18CXhDb1ygxg-YXNBJNzfzZsDFosB5e6BfnXLlejd9l0/edit

1. The steering committee hasn't given the go ahead for this yet, and we have 
no idea when such a decision will be made nor whether the decision with be yes 
or no.

2. Even after the decision is made "Removing the GIL will be a large, 
multi-year undertaking with increased risk for introducing bugs and 
regressions."

3. The promised performance gains are actually small by comparison to the 
existing project that Guido is running is hoping to achieve. It is unclear 
whether the no-gil implementation would impact those gains, and if so whether a 
small reduction in the large planned performance gains would actually more than 
wipe out the modest performance gains promised by the no-gil project.

4. Given that this "Removing the GIL will require making trade-offs and taking 
on substantial risk", it is easy to see that this project could come across an 
unacceptable risk or insurmountable technical problem at any point and thus 
fall by the wayside.

Taking all of the above points together, I think that there is still merit in 
considering the pros and cons of a GIL scheduler.

--

___
Python tracker 
<https://bugs.python.org/issue7946>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue7946] Convoy effect with I/O bound threads and New GIL

2022-03-21 Thread Sophist


Sophist  added the comment:

> I think that we should focus our efforts on removing the GIL, now that we 
> have a feasible solution for doing so without breaking anything

Is this really a thing? Something that is definitely happening in a reasonable 
timescale?

Or are there some big compatibility issues likely to rear up and at best create 
delays, and at worse derail it completely?

Can someone give me some links about this please?

--

___
Python tracker 
<https://bugs.python.org/issue7946>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue7946] Convoy effect with I/O bound threads and New GIL

2022-03-21 Thread Sophist


Sophist  added the comment:

Please see also https://github.com/faster-cpython/ideas/discussions/328 for a 
proposal for a simple (much simpler than BFS) GIL scheduler only allocating the 
GIL between runable O/S threads waiting to have ownership of the GIL, and using 
the O/S scheduler for scheduling the threads.

--
nosy: +Sophist

___
Python tracker 
<https://bugs.python.org/issue7946>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue16283] ctypes.util.find_library does not find all DLLs anymore

2017-05-13 Thread Sophist

Sophist added the comment:

http://stackoverflow.com/questions/23125857/python-os-path-exists-cant-locate-the-file-however-the-file-indeed-exsits
 gave me an explanation:

That when running 32-bit apps on Win 64 C:\Windows\SysWOW64 is mapped to 
C:\Windows\system32.

Copying the missing DLL to SysWOW64 made it work.

NOTE: Original report was for 64-bit on 64-bit, so this is not necessarily an 
explanation of the original issue.

--

___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue16283>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue16283] ctypes.util.find_library does not find all DLLs anymore

2017-05-13 Thread Sophist

Changes by Sophist <pyt...@sodalis.co.uk>:


--
versions:  -Python 3.7

___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue16283>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue16283] ctypes.util.find_library does not find all DLLs anymore

2017-05-13 Thread Sophist

Changes by Sophist <pyt...@sodalis.co.uk>:


--
versions: +Python 2.7, Python 3.4, Python 3.5, Python 3.6, Python 3.7

___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue16283>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue16283] ctypes.util.find_library does not find all DLLs anymore

2017-05-13 Thread Sophist

Sophist added the comment:

Finding it impossible for PIP to install discid.

Tracked it down to this issue i.e. 
os.path.isfile('C:\Windows\system32\discid.dll') == False when the dll exists.

Some other dlls in that directory result in True and some in False. I cannot 
see any significant difference in security permissions that might cause this - 
only difference is security permissions for some are inherited and some are not 
inherited.

I get this on both Python 3.6.1 32-bit and 2.7.13 32-bit on Win 10 Pro 64-bit 
Anniversary Edition 1607. I use ESET Smart Security 9 as AV.

--
nosy: +Sophist

___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue16283>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com