TGINSIGHT SIMILAR POSTS
Source channel @pythontelegrambotchannel · Post #89 · Oct 7
The v13 release is not just a release either, it is also our official announcement of participation in the annual #hacktoberfest. 💻🥨 We know that we're a few days late to the party, but v13 had to get ready before. 😉 This year, the fest is opt-in for projects and we definitely want to opt into taking part in this great event! If you ever thought about starting coding or giving back to your favourite open source repositories, now is the time! Head over to the hacktoberfest website to learn more about it. We already prepared some issues on our repositories and aim towards opening more issues for starters, but feel free to begin a hunt for improvements and fixes by yourself!
Hashtags
Search: #scheduled
@luckydonaldsbots · Post #290 · 12/11/2021, 10:33 PM
Also there will be a scheduled downtime for two remaining bots tomorrow, in about 16h 20h from now : - @BanWarnBot - @RulesRulesBot Those have a database, and therefore they need to be take down to not loose any changes happining while the data is moved over. #scheduled#downtime
Hashtags
@djangoproject · Post #92 · 07/11/2016, 11:59 AM
https://docs.python.org/3/library/asyncio-dev.html#asyncio-coroutine-not-scheduled 18.5.9.6. Detect #coroutine objects never #scheduled When a coroutine function is called and its result is not passed to ensure_future() or to the BaseEventLoop.create_task() method, the execution of the coroutine object will never be scheduled which is probably a bug. Enable the debug mode of asyncio to log a warning to detect it. Example with the bug: import asyncio @asyncio.coroutine def test(): print("never scheduled") test() Output in debug mode: Coroutine test() at test.py:3 was never yielded from Coroutine object created at (most recent call last): File "test.py", line 7, in <module> test() The fix is to call the ensure_future() function or the BaseEventLoop.create_task() method with the coroutine object.
Hashtags