Some warnings under Python 3.8.0
See original GitHub issue/opt/mtprotoproxy/mtprotoproxy.py:2190: DeprecationWarning: The loop argument is deprecated since Python 3.8, and scheduled for removal in Python 3.10.
servers.append(loop.run_until_complete(task))
/opt/mtprotoproxy/mtprotoproxy.py:2195: DeprecationWarning: The loop argument is deprecated since Python 3.8, and scheduled for removal in Python 3.10.
servers.append(loop.run_until_complete(task))
An open stream object is being garbage collected; call "stream.close()" explicitly.
Could you fix it please?
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Deprecation and syntax warnings in Python 3.8 #1554 - GitHub
Deprecation warning due to invalid escape sequences. Using raw strings or escaping them again helps in resolving this. Syntax warnings due to comparison...
Read more >warnings — Warning control — Python 3.11.1 documentation
Warning messages are typically issued in situations where it is useful to alert the user of some condition in a program, where that...
Read more >Python 3.8.0 always get either linting warning ... - Stack Overflow
If I do from pets import Dog from main.py, I get a linter warning on the latest versions of pylint, flake8, and bandit....
Read more >Python 3.8: Cool New Features for You to Try
In this article, you'll learn about: Using assignment expressions to simplify some code constructs; Enforcing positional-only arguments in your ...
Read more >What's new in Python 3.8? - DeepSource
While there's still some time before the final stable version is available, it is worth looking into all that's new. Python 3.8 adds...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Looks like this bug in Python: https://bugs.python.org/issue38529. So you can ignore it. Will likely be fixed by 3.8.1. But I’ll try to install Python 3.8 and investigate this a bit
Ok, the loop argument is removed, https://github.com/alexbers/mtprotoproxy/commit/fd75ca3cf901fab61e6e22b197acf18d26fb02a5. The asyncio is becoming better, I like it.