Change by Andrew Svetlov :
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Change by Andrew Svetlov :
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Andrew Aladjev added the comment:
Hello, it seems like issue 22724 is completely the same. Let's discuss
solutions there. Thank you.
--
___
Python tracker
<https://bugs.python.org/is
Change by Andrew Aladjev :
--
nosy: +puchenyaka
___
Python tracker
<https://bugs.python.org/issue22724>
___
___
Python-bugs-list mailing list
Unsubscribe:
Andrew Aladjev added the comment:
Hello. I've provided a double recompilation workaround in the following gentoo
bug https://bugs.gentoo.org/705970. You can use it for now if you don't want to
wait until this issue will be fixed.
I will try patches provided by people in this iss
Andrew Aladjev added the comment:
I've made a quick test of all patches provided. All patches have failed to fix
it. The problem is more heavy than it looks like.
Please look at the following code:
PYTHON_FOR_BUILD='_PYTHON_PROJECT_BASE=$(abs_builddir)
_PYTHON_HOS
Andrew Svetlov added the comment:
The latest example releases allocated python objects.
The memory is returned to allocator which, in turn, can hold it for a while.
The allocator is not controlled by Python API.
Anyway, if an explicit executor solves your needs -- please just use it
Andrew Svetlov added the comment:
Serhiy is right, I doubt if we can do something here.
A function address is a part of its __repr__() output.
--
nosy: +asvetlov
___
Python tracker
<https://bugs.python.org/issue39
Andrew Svetlov added the comment:
-1.
I rather suggest updating telethon example in the following matter:
async with main():
with TelegramClient('anon', api_id, api_hash) as client:
await client.send_message('me', 'Hello, myself!')
You PR brings more
Andrew Svetlov added the comment:
A client that creates a loop implicitly in the constructor is a weird design
from my perspective.
You are free to use it, sure -- but please let us keep the freedom to not
support such corner cases by asyncio.run()
Sorry, I don't know the telethon li
Andrew Svetlov added the comment:
Explicit error is better than error-prone design.
Think that we will deprecate asyncio.get_event_loop() and the loop
instantiation on-demand in the main thread.
--
resolution: -> rejected
stage: patch review -> resolved
status: open -&g
Andrew Svetlov added the comment:
New changeset 90d9ba6ef10af32e8dfe0649789c3a8ccf419e95 by Andrew Svetlov in
branch 'master':
bpo-34793: Drop old-style context managers in asyncio.locks (GH-17533)
https://github.com/python/cpython/commit/90d9ba6ef10af32e8dfe0649789c3a
Change by Andrew Svetlov :
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Change by Andrew Svetlov :
--
resolution: -> wont fix
status: open -> closed
___
Python tracker
<https://bugs.python.org/issue39483>
___
___
Python-bugs-
New submission from Andrew Svetlov :
Yuri proposed it for Python 3.8 but at that time the change was premature.
Now we can reconsider it for 3.9
The problem is that asyncio.get_event_loop() not only returns a loop but also
creates it on-demand if the thread is main and the loop doesn't
Andrew Svetlov added the comment:
Currently, I'm talking about adding a deprecation only.
The asyncio.get_event_loop() function will stay in Python for a while in
deprecated status. I don't know the exact period but it should be 3 releases at
least I guess, with possibly exte
Andrew Svetlov added the comment:
Serhiy, maybe I had not understood your proposal properly.
If you are asking about deprecating get_event_loop() call from outside of async
code but implicit call get_running_loop() without a warning if called from
async function -- it sounds like a
Change by Andrew Svetlov :
--
components: +asyncio
nosy: +yselivanov
___
Python tracker
<https://bugs.python.org/issue39529>
___
___
Python-bugs-list mailin
Change by Andrew Svetlov :
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Change by Andrew Svetlov :
--
nosy: -asvetlov
___
Python tracker
<https://bugs.python.org/issue10572>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Andrew Svetlov :
--
assignee: -> asvetlov
nosy: +asvetlov
___
Python tracker
<https://bugs.python.org/issue34788>
___
___
Python-bugs-list mai
Change by Andrew Svetlov :
--
keywords: +patch
pull_requests: +17831
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/18457
___
Python tracker
<https://bugs.python.org/issu
Andrew Svetlov added the comment:
Victor, sorry.
I spent about 4 days in total trying to figure out what is the reason for
hanging.
I see that the signal handler is installed; but, in a rare situation, it is not
called when the process is killed.
If I reduce an amount of code executed in a
New submission from Andrew Wall :
I encountered a question on Stackoverflow where, unusually, a Traceback was
given in full, but I couldn't diagnose the problem.
It was like this:
Traceback (most recent call last):
File "soFailedTraceback.py", line 15, in
c = C(C
Andrew Svetlov added the comment:
The ship has sailed, this change breaks a lot of existing code without a strong
reason.
I recall very many cases in third-party libraries and commercial applications
where a negative argument for asyncio.sleep() is processed as asyncio.sleep(0)
without
Andrew Svetlov added the comment:
Not so easy to find a satisfactory generic approach.
An argument can also be 10 MiB length bytes array, a dictionary with 10,000
elements, HTML page, name it.
All these objects are printable but their representation is too verbose.
Task can have a dozen of
Andrew Bartlett added the comment:
This breaks Samba's build:
https://bugzilla.samba.org/show_bug.cgi?id=14266
While we are of course able to patch new versions of Samba, this will make it
harder to bisect back though Samba history. It would be really great if this
kind of change cou
Andrew Svetlov added the comment:
The second solution doesn't help with breaking infinite loops like
while True:
pass
We need a more robust idea.
--
___
Python tracker
<https://bugs.python.org/is
Andrew Svetlov added the comment:
>From my understanding, the issue is still desirable but we have a lack of
>resources.
Regarding the patch for tornado, using selectors.SelectSelector for
implementing add_reader()/remove_reader() and add_writer()/remove_writer() in
ProactorEventLoop
Andrew Svetlov added the comment:
I'm not sure.
Logging can pollute the logger and make it almost useless.
Most of mentioned errno codes are programming errors, a few may happen due
network issues.
Would you share what reasons did you ob
Andrew Svetlov added the comment:
For server applications, the reverse proxy in front of the application can
limit the connection limit.
It is a good workaround because the proxy is required (and most likely is used
already) for any non-trivial server app
Change by Andrew Svetlov :
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Andrew Svetlov added the comment:
Thanks, Ido
--
___
Python tracker
<https://bugs.python.org/issue39128>
___
___
Python-bugs-list mailing list
Unsubscribe:
Andrew Svetlov added the comment:
The behavior is intentional and follows asyncio.run() semantics.
Moreover, every test should have a separate event loop instance, this is
stressed by IsolatedAsyncioTestCase class name
--
resolution: -> wont fix
stage: -> resolved
status
Andrew Svetlov added the comment:
asyncio doesn't kill subprocess by timeout, that's why test1() doesn't work.
The kill is done by signal sending which is asynchronous. That's why test2 may
fail at "FAIL(3)" point sometimes.
1-second sleep is enough to stop t
Andrew Svetlov added the comment:
This is a very interesting question.
In asyncio, task cancellation is not executed on `task.cancel()` call
immediately but the task is *marked* for cancellation.
The actual cancellation requires a context switch (await asyncio.sleep(0) or
similar) to
Change by Andrew Svetlov :
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Andrew Svetlov added the comment:
I consider a free type for the default as an implementation detail, not the
encouraged approach.
Since the value is always a string, using the same type for the default sounds
like a sane design for me.
--
nosy: +asvetlov
Andrew Svetlov added the comment:
I'm sorry. but loop.set_signal_handler() method doesn't exist.
--
___
Python tracker
<https://bugs.python.o
Andrew Svetlov added the comment:
Assuming you mean loop.add_signal_handler() method, I would say that a
minute-long delay is a sign of long blocking calls in your program.
Typical asyncio program blocks the loop for 1-10 milliseconds at most, and
signal handlers are called with this delay
Andrew Svetlov added the comment:
Other threads are not related.
Speaking about the main thread that runs an event loop with the signal handler
installed -- the handler is executed along with other async code.
If the loop executes some user-provides async task -- it executes the signal
Change by Andrew Svetlov :
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Andrew Svetlov added the comment:
New changeset 4482337decdbd0c6e2150346a68b3616bda664aa by Lidi Zheng in branch
'master':
bpo-39764: Make Task.get_stack accept ag_frame (#18669)
https://github.com/python/cpython/commit/4482337decdbd0c6e2150346a68b36
Change by Andrew Svetlov :
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Andrew Bartlett added the comment:
Thanks for the reply.
To clarify, it is best to understand where Samba thinks of itself in terms of
Python. We use python, but we don't really think of ourselves as a python
project, and while we have some developers with a depth of experience i
Andrew Bartlett added the comment:
I think we are speaking past each other.
Yes, Python 2 is no longer being changed, which is awesome as we need for fear
breakage of the older builds that use that for the build system.
The issue isn't the particular language feature, or that there
Andrew Bartlett added the comment:
...Python 2.9 or at best 2.10.
Of course I mean Python 3.9 or at best 3.10.
Sorry for the confusion.
--
___
Python tracker
<https://bugs.python.org/issue37
Andrew Svetlov added the comment:
Would somebody be a champion for the issue?
--
___
Python tracker
<https://bugs.python.org/issue39148>
___
___
Python-bug
Change by Andrew Nelson :
--
nosy: +Andrew Nelson
___
Python tracker
<https://bugs.python.org/issue38501>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Andrew Zhou :
This isn't a particularly high priority, but it would be nice to have the first
paragraph of docs pages show up when searched or posted in Slack, Discord,
Twitter, etc. This is done through the description meta tag, as well as Open
Graph, etc. A
New submission from Andrew Black :
The documentation for the built-in function next (which calls the __next__
method on an iterator) discusses its behavior when the iterator is exhausted.
It talks about the StopIteration exception. However, it does not say anything
about calling next with
Andrew Svetlov added the comment:
New changeset f5a19ead4ba8c81cc27d5a530f830f4709ce240e by Soumendra Ganguly in
branch 'master':
bpo-41818: Make test_openpty() avoid unexpected success due to number of rows
and/or number of columns being == 0. (GH-23526)
https://github.com/pyth
Andrew Svetlov added the comment:
New changeset e4fe303b8cca525e97d44e80c7e53bdab9dd9187 by Yurii Karabas in
branch 'master':
bpo-42392: Remove loop parameter from asyncio.tasks and asyncio.subprocess
(GH-23521)
https://github.com/python/cpyt
Change by Andrew Svetlov :
--
resolution: -> wont fix
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.org/issue42466>
___
___
Andrew Svetlov added the comment:
Partially addressed by https://github.com/python/cpython/pull/21735
--
___
Python tracker
<https://bugs.python.org/issue42
Change by Andrew Svetlov :
--
title: remove the 'loop' parameter from __init__ in all classes in
asyncio.locks -> remove the deprecated 'loop' parameter asyncio API
___
Python tracker
<https://
Andrew Svetlov added the comment:
Fixed by #42392
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
superseder: -> remove the deprecated 'loop' parameter asyncio API
versions: +Python 3.10 -Python 3.9
Change by Andrew Svetlov :
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Andrew Svetlov added the comment:
New changeset 8085f742f4adfbc85f13fc734dfab036aa23acfb by Zackery Spytz in
branch 'master':
bpo-34215: Clarify IncompleteReadError message when "expected" is None
(GH-21925)
https://github.com/python/cpython/commit/8085f742f4adfbc85f13
Change by Andrew Svetlov :
--
versions: +Python 3.8, Python 3.9
___
Python tracker
<https://bugs.python.org/issue34215>
___
___
Python-bugs-list mailin
Andrew Svetlov added the comment:
Can we close the issue?
--
nosy: +asvetlov
___
Python tracker
<https://bugs.python.org/issue41756>
___
___
Python-bugs-list m
Andrew Svetlov added the comment:
New changeset 4498e98a6bdf017d3b65fa679baf4c797909beb6 by Miss Islington (bot)
in branch '3.8':
bpo-34215: Clarify IncompleteReadError message when "expected" is None
(GH-21925) (#23540)
https://github.com/p
Andrew Svetlov added the comment:
New changeset d41ec65ab7411e877ca33d05e8c900feca530635 by Zackery Spytz in
branch 'master':
bpo-42489: Fix the signature for list.sort() in the tutorial (GH-23538)
https://github.com/python/cpython/commit/d41ec65ab7411e877ca33d05e8c900
Andrew Svetlov added the comment:
New changeset df6c8bcffef3380869c8f76317610ce452880b25 by Miss Islington (bot)
in branch '3.9':
bpo-34215: Clarify IncompleteReadError message when "expected" is None
(GH-21925) (GH-23539)
https://github.com/p
Change by Andrew Svetlov :
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Andrew Svetlov added the comment:
Fixing a non-broken thing is not a world-class idea, I think.
--
___
Python tracker
<https://bugs.python.org/issue41
Change by Andrew Svetlov :
--
assignee: -> docs@python
components: +Documentation -macOS
nosy: +docs@python
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
versions: +Python 3.10, Python 3.8
___
Python tra
Andrew Svetlov added the comment:
Both mentioned links have the correct code.
They use sync __aiter__ and async __anext__
--
resolution: -> out of date
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bug
Andrew Svetlov added the comment:
New changeset 74311aeb45b52cc145d27d9fca99f01874d6882d by Soumendra Ganguly in
branch 'master':
bpo-41818: Fix test_master_read() so that it succeeds on all platforms that
either raise OSError or return b"" upon reading from mas
Andrew Svetlov added the comment:
You are right.
--
___
Python tracker
<https://bugs.python.org/issue41879>
___
___
Python-bugs-list mailing list
Unsubscribe:
Andrew Svetlov added the comment:
New changeset 86150d39c888579b65841f4391d054b7b3eff9f2 by Yurii Karabas in
branch 'master':
bpo-42392: Remove deprecated loop parameter from docs (GH-23552)
https://github.com/python/cpython/commit/86150d39c888579b65841f4391d054
Andrew Svetlov added the comment:
Thanks for your help!
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Andrew Svetlov added the comment:
This is a deliberate decision.
An exception in handling one client connection should not break another
connected client.
--
___
Python tracker
<https://bugs.python.org/issue42
Andrew Svetlov added the comment:
Agree, not a bug.
--
resolution: -> not a bug
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Andrew Svetlov added the comment:
You can use try/except in handler() and dispatch the exception whatever you
want.
It doesn't require a new asyncio version, debug-only flag, etc.
--
___
Python tracker
<https://bugs.python.org/is
Andrew Svetlov added the comment:
I understand the issue as the following:
1. You don't save the result of `asyncio.create_task()` somewhere.
The task object is dereferenced and thus you see a warning.
2. With PYTHONASYNCIODEBUG on the task is referenced also by internal debug
stru
Andrew Svetlov added the comment:
Moreover, the issue is outdated.
asyncio.CancelledError is not an alias of concurrent.futures.CancelledError
starting from Python 3.8
Unfortunately, we should make this not 100% backward compatible change.
--
nosy: +asvetlov
Change by Andrew Svetlov :
--
resolution: -> out of date
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Andrew Svetlov added the comment:
Sorry, this issue is not reproduced on 3.8-3.9, 3.7 is in security mode.
The issue doesn't belong to the security set.
Closing.
--
resolution: -> out of date
stage: -> resolved
status: open -> closed
Andrew Svetlov added the comment:
Thanks for the report.
I didn't test but looks like `outer.exception()` call can suppress the message
about not retrieved exception.
--
___
Python tracker
<https://bugs.python.org/is
Andrew Svetlov added the comment:
Reporting what? Please elaborate.
--
___
Python tracker
<https://bugs.python.org/issue42644>
___
___
Python-bugs-list mailin
Change by Andrew Svetlov :
--
components: +Library (Lib) -asyncio
___
Python tracker
<https://bugs.python.org/issue42644>
___
___
Python-bugs-list mailin
Change by Andrew Svetlov :
--
type: crash -> behavior
___
Python tracker
<https://bugs.python.org/issue42644>
___
___
Python-bugs-list mailing list
Unsubscrib
Andrew Svetlov added the comment:
New changeset b32d8b4f9bcd2e7d11240b6b9de0262cf8f5e09d by Matthias Bussonnier
in branch 'master':
bpo-42644: Validate values in logging.disable() (#23786)
https://github.com/python/cpython/commit/b32d8b4f9bcd2e7d11240b6b9de026
Change by Andrew Svetlov :
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
versions: +Python 3.10, Python 3.8, Python 3.9 -Python 3.7
___
Python tracker
<https://bugs.python.or
Andrew Svetlov added the comment:
New changeset 66d3b589c44fcbcf9afe1e442d9beac3bd8bcd34 by Chris Jerdonek in
branch 'master':
bpo-38323: Add guard clauses in MultiLoopChildWatcher. (#22756)
https://github.com/python/cpython/commit/66d3b589c44fcbcf9afe1e442d9bea
Andrew Svetlov added the comment:
New changeset ba760f3710eccdfae2b680a5f94fe0160ddb1536 by pxinwr in branch
'master':
bpo-31904: Skip some asyncio tests on VxWorks (#23815)
https://github.com/python/cpython/commit/ba760f3710eccdfae2b680a5f94fe0160ddb1536
--
nosy:
Andrew Svetlov added the comment:
The traceback contains frames from asyncio internal machinery, that's why the
traceback is long.
IFIAK Python standard library never filters such calls, asyncio is not an
exception.
On the other hand, well-known pytest library supports `__tracebackh
Andrew Svetlov added the comment:
New changeset d90ff376813843310a6f9ccc96551fa1521e8fef by Matt Fowler in branch
'master':
BPO-42703: Fix incorrect documentation links for asyncio.Event (GH-23881)
https://github.com/python/cpython/commit/d90ff376813843310a6f9ccc96551f
Change by Andrew Svetlov :
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Change by Andrew Brunner :
--
nosy: +abrunner73
___
Python tracker
<https://bugs.python.org/issue22213>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Andrew MacDonald :
When attempting to read a large file (> 2GB) over HTTPS the read fails with
"OverflowError: signed integer is greater than maximum".
This occurs with Python >=3.8 and I've been able to reproduce the problem with
the below snippet
New submission from Andrew C :
if playerChoice == "2": reports the ":" as a "syntax error"
--
components: Windows
messages: 385427
nosy: ASCRong, paul.moore, steve.dower, tim.golden, zach.ware
priority: normal
severity: normal
status: open
title: Bug
type:
Andrew Borba added the comment:
> The key word here is "misbehaving". Cooperative concurrency does require
> cooperation.
Your stance makes sense in an ideal environment where we control every Task
that our application deals with. However, there are some cases in wh
Andrew Tomazos added the comment:
The problem occurs if you:
#include
on *nix systems. Note `/usr/include/` is in the system include path. One
workaround is to `-I/usr/include/python3.8` and then `#include `.
Another workaround is to comment out:
// #include "cp
Andrew Tomazos added the comment:
Related: https://stackoverflow.com/q/63211981/1131467
--
___
Python tracker
<https://bugs.python.org/issue40642>
___
___
Pytho
Andrew Tomazos added the comment:
After studying the include directives in the Include folder, I think the best
fix would be:
In Include/cpython/state.h:
- #include "cpython/initconfig.h"
+ #include "initconfig.h"
this will mean that state.h will find initc
Andrew Svetlov added the comment:
I agree with Yuri.
Usually, you don't need overriding of the default exception handler.
Indeed, if you really need this low-level API I see nothing wrong with
`asyncio.get_running_loop()` call.
--
___
P
Change by Andrew Svetlov :
--
resolution: -> wont fix
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Andrew Svetlov added the comment:
Remi is correct.
Closing the issue.
--
___
Python tracker
<https://bugs.python.org/issue41242>
___
___
Python-bugs-list mailin
901 - 1000 of 3160 matches
Mail list logo
