David Mertz writes:
> On Wed, Feb 24, 2021 at 1:38 PM Paul Korir wrote:
>
> > I've been using the argparse library for a long time and one use case that
> > repeatedly shows us is the need to have two arguments appear together i.e
> > either both appear or none of them appear. I'll refer to
> On 25 Feb 2021, at 17:15, Jonathan Slenders wrote:
>
> It does make sense to have a barrier synchronization primitive for asyncio.
> The idea is to make a coroutine block until at least X coroutines are waiting
> to enter the barrier.
> This is very useful, if certain actions need to be
Hi Jonathan
Le 25/02/2021 à 18:15, Jonathan
Slenders a écrit :
It does make sense to have a barrier synchronization
primitive for asyncio.
The idea is to make a coroutine block until at least X
coroutines are
On 2021-02-25 01:05, Steven D'Aprano wrote:
On Wed, Feb 24, 2021 at 06:46:21PM -0800, Mike Miller wrote:
Also, I don't believe the confusion mentioned was regarding syntax, but
rather a word that most people have never heard before.
When I started learning Python, back when 1.5 was new and
On Thu, 25 Feb 2021 at 19:22, Mike Miller wrote:
> Mr. Random had an interesting point to start this thread, that over-reliance
> on
> venvs may have slowed fixes and improvements on the standard tools and
> distributions. I suspect there is some truth to the assertion.
Arguably, your claim
On 2021-02-24 19:59, Christopher Barker wrote:
I used to do that — for years. But it really did cause problems.
The trick is that you have, say, your 57 apps all working. Then you need to
update a package for one. As soon as you update, you have to go test your 57
apps, and if one of them is
It does make sense to have a barrier synchronization primitive for asyncio.
The idea is to make a coroutine block until at least X coroutines are
waiting to enter the barrier.
This is very useful, if certain actions need to be synchronized.
Recently, I had to implement a barier myself for our use
> On 25 Feb 2021, at 13:14, Yves Duprat wrote:
>
> Hi,the list,
>
> I'm wondering why Barrier object does not exist in the synchronization
> primitives of the asyncio lib while it is present in threading and
> multiprocessing libs ?
> This may not be the right place to ask this question,
Hi,the list,
I'm wondering why Barrier object does not exist in the synchronization
primitives of the asyncio lib while it is present in threading and
multiprocessing libs ?
This may not be the right place to ask this question, but I never found an
answer on the web.
Thanks for your help.
On Wed, Feb 24, 2021 at 06:46:21PM -0800, Mike Miller wrote:
> Also, I don't believe the confusion mentioned was regarding syntax, but
> rather a word that most people have never heard before.
When I started learning Python, back when 1.5 was new and cutting edge,
it was an embarassingly long
10 matches
Mail list logo
