On Mon, Nov 05, 2018 at 07:15:04PM -0700, Ian Kelly wrote:
> > For context:
> > https://github.com/ldo/dbussy/issues/13
> > https://gist.github.com/tu500/3232fe03bd1d85b1529c558f920b8e43
> >
> > It really feels like asyncio is loosing strong references to scheduled
> > tasks, as excplicitly keeping
On Mon, Nov 5, 2018 at 6:20 PM wrote:
> Again sorry for the confusion, but I don't think this is an issue with
> restarting loops, as this isn't happening in my application.
Sure, I wasn't talking about restarting loops so much as strategies
for making sure that everything has completed in the fi
On Mon, Nov 05, 2018 at 01:57:56PM -0700, Ian Kelly wrote:
> > Which is what I want in this case. Scheduling a new (long-running) task
> > as a side effect, but returning early oneself. The new task can't be
> > awaited right there, because the creating one should return already.
>
> If you want t
On Tue, Nov 06, 2018 at 12:45:03AM +0100, i...@koeln.ccc.de wrote:
> Also, I may be overlooking things, but I haven't found a way to add a
> task before calling run_forever(), as asyncio will then say the loop
> isn't running yet. So I'm not sure how you would jumpstart in that case.
Ok, I was con
On Mon, Nov 05, 2018 at 01:57:56PM -0700, Ian Kelly wrote:
> > Which is what I want in this case. Scheduling a new (long-running) task
> > as a side effect, but returning early oneself. The new task can't be
> > awaited right there, because the creating one should return already.
>
> If you want t
On Mon, Nov 5, 2018 at 8:41 AM wrote:
> > > But anyway, I highly recommend you to use the "await other_coroutine()"
> > > syntax I talked about earlier. It may even fix the issue (90% chance).
> >
> > This should indeed fix the issue, but this is definitely not what one is
> > looking for if one r
On 05/11/2018 16:38, i...@koeln.ccc.de wrote:
> I just saw, actually
> using the same loop gets rid of the behavior in this case and now I'm
> not sure about my assertions any more.
It's fixing the issue because you're running loop with the
run_forever(). As Ian and myself pointed out, using both
On 11/4/18 8:55 AM, Mike C wrote:
Same here. Debugging in Python is annoying, I like to step through my code line
by line, it's impossible to do it with object-oriented programming language.
Also, there's no good REPL IDE.
Spyder barely works with some basic features. PyCharm, the most popular
This weird mixing was actually a side effect of me quickly coming up
with a small example, sorry for the confusion. I just saw, actually
using the same loop gets rid of the behavior in this case and now I'm
not sure about my assertions any more. Yet it still looks like asyncio
doen'st keep strong r
Jacob, please reply to the list, not to me personally. As I said, I
have no idea about gmpy2 or pip, I just know how to google.
On 01/11/2018 23:28, jacob m wrote:
I tried to install libgmp3-dev, but it didn't solved my problem
On Thu, 1 Nov 2018 at 18:44, Rhodri James wrote:
Replying to t
Sorry Rhodri, my gmail set your email as default recipient when I was
responding, I forgot to change that. Sorry for that
Regards
On Mon, 5 Nov 2018 at 13:06, Rhodri James wrote:
> Jacob, please reply to the list, not to me personally. As I said, I
> have no idea about gmpy2 or pip, I just know
On 05/11/2018 10:00, Thomas Jollans wrote:
On 2018-11-05 10:47, Robin Becker wrote:
raise ImportError('This package should not be accessible on Python 3. '
'Either you are trying to run from the python-future src
folder '
'or your installation
On 2018-11-05 10:47, Robin Becker wrote:
> raise ImportError('This package should not be accessible on Python 3. '
> 'Either you are trying to run from the python-future
> src folder '
> 'or your installation of python-future is corrupted.')
It woul
On 05/11/2018 07:55, Ian Kelly wrote:
>> I assume it's kind of a run_forever() with some code before it
>> to schedule the coroutine.
>
> My understanding of asyncio.run() from
> https://github.com/python/asyncio/pull/465 is that asyncio.run() is
> more or less the equivalent of loop.run_until_com
For some reason I find my windows 32 bit python 2.7.13 has a package called builtins installed in site-packages. This creates
confusion about how to look at builtins.
The __init__.py looks like this
from __future__ import absolute_import
import sys
__future_module__ = True
if sys.version_info
15 matches
Mail list logo
