Brian Quinlan added the comment:
That's a super interesting bug! It looks like this issue is that your exception
can't be round-tripped using pickle i.e.
>>> class PoolBreaker(Exception):
... def __init__(self, num):
... super().__init__()
...
New submission from Brian Quinlan :
$ ./python.exe nopickle.py
TypeError: __init__() missing 1 required positional argument: 'num'
The issue is that the arguments passed to Exception.__init__ (via `super()`)
are collected into `args` and then serialized by pickle e.g.
>>&
Change by Brian Quinlan :
--
title: picke cannot dump exceptions subclasses with different super() args ->
picke cannot dump Exception subclasses with different super() args
___
Python tracker
<https://bugs.python.org/issu
Change by Brian Quinlan :
--
resolution: -> duplicate
superseder: -> picke cannot dump Exception subclasses with different super()
args
___
Python tracker
<https://bugs.python.org/i
Change by Brian Quinlan :
--
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.org/issue37208>
___
___
Python-bugs-list
Change by Brian Quinlan :
--
resolution: -> duplicate
stage: -> resolved
status: open -> closed
superseder: -> function changed when pickle bound method object
___
Python tracker
<https://bugs.python
Brian Quinlan added the comment:
New changeset 242c26f53edb965e9808dd918089e664c0223407 by Brian Quinlan in
branch 'master':
bpo-31783: Fix a race condition creating workers during shutdown (#13171)
https://github.com/python/cpython/commit/242c26f53edb965e9808dd918089e6
Change by Brian Quinlan :
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Brian Quinlan added the comment:
I don't know what the backport policy is. The bug is only theoretical AFAIK
i.e. someone noticed it through code observation but it has not appeared in
the wild.
On Mon, Jul 1, 2019 at 3:25 PM Ned Deily wrote:
>
> Ned Deily added the comment
Brian Quinlan added the comment:
Can I add "needs backport to 3.8" and "needs backport to 3.7" labels now or
do I have to use cherry_picker at this point?
On Mon, Jul 1, 2019 at 3:55 PM Ned Deily wrote:
>
> Ned Deily added the comment:
>
> > I don't
Change by Brian Skinn :
--
type: enhancement -> behavior
___
Python tracker
<https://bugs.python.org/issue37699>
___
___
Python-bugs-list mailing list
Un
New submission from Brian Skinn :
Once the underlying buffer/stream is .detach()ed from an instance of a subclass
of TextIOBase or BufferedIOBase, accession of most attributes defined on
TextIOBase/BufferedIOBase or the IOBase parent, as well as calling of most
methods defined on TextIOBase
Brian Skinn added the comment:
Mm, agreed--that regex wouldn't be hard to write.
The problem is, AFAICT there's irresolvable syntactic ambiguity in a line
starting with exactly three periods, if the doctest PS2 specification is not
constrained to be exactly "... &q
Brian Skinn added the comment:
I suppose one alternative solution might be to tweak the ELLIPSIS feature of
doctest, such that it would interpret a run of >=3 periods in a row (matching
regex pattern of "[.]{3,}") as 'ellipsis'.
The regex for PS2 could then have a n
Brian Skinn added the comment:
On reflection, it would probably be better to limit the ELLIPSIS to 3 or 4
periods ('[.]{3,4}'); otherwise, it would be impossible to express an ellipsis
followed by a period in a 'want'.
--
__
Brian Thorne added the comment:
Hi Robert, It would be at least a week or two before I could take another look
at this so please feel free to work on it. Not sure why I didn't write a patch
at the time!
--
___
Python tracker
Brian Moyles added the comment:
I ran into the same problem when running the test suite against a fresh Python
3.6.2 build on Ubuntu 16.04. It specifically appears to be a problem with ndbm
and retrieving an empty byte string value:
Python 3.6.2 (default, Sep 8 2017, 18:31:28)
[GCC 5.4.0
Brian Moyles added the comment:
Actually, I was able to make things happy by removing libdb5.3-dev and solely
relying on libgdbm3-dev (which suggests that Debian upstream may want to pare
back their build requirements rather than disable the dbm test as they appear
to do now
New submission from Brian Moyles:
In building Python 3.6.2 on Ubuntu 16.04, test_socket repeatedly fails at
==
FAIL: testWithTimeoutTriggeredSend (test.test_socket.SendfileUsingSendfileTest
New submission from Brian Moyles:
In building Python 3.6.2 on Ubuntu 16.04, test_socket repeatedly fails at
==
FAIL: testWithTimeoutTriggeredSend (test.test_socket.SendfileUsingSendfileTest
Brian Moyles added the comment:
accidental double-submit, duplicates Issue31436
--
resolution: -> duplicate
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
New submission from Brian Maissy :
If a call to select.select() was interrupted by a signal and the select syscall
set an errno of EINTR, then under PEP 475 the select call should be re-executed.
If, however, there is a signal handler which takes enough time that the
select's timeout ex
Brian Maissy added the comment:
I believe the offending line in the source is this break statement:
https://github.com/python/cpython/blob/master/Modules/selectmodule.c#L339
--
___
Python tracker
<https://bugs.python.org/issue35
Brian Maissy added the comment:
The current behavior is:
> select() is not retried, and the rlist is returned as-is (with fds in it
> which are not ready for reading)
Yes, this is a bug. It results in select() indicating that fd are ready for
reading when they, in fact, a
Change by Brian Maissy :
--
nosy: +oranav
___
Python tracker
<https://bugs.python.org/issue35310>
___
___
Python-bugs-list mailing list
Unsubscribe:
Brian Curtin added the comment:
New changeset e394ba32147f687b6bc7518d461f1d84211698e0 by Brian Curtin
(Charles-Axel Dein) in branch 'master':
bpo-35404: Clarify how to import _structure in email.message doc (GH-10886)
https://github.com/python/cpyt
Brian Curtin added the comment:
New changeset 478f8291327a3e3ab17b5857699565df43a9e952 by Brian Curtin (Ashwin
Ramaswami) in branch 'master':
bpo-21257: document http.client.parse_headers (GH-11443)
https://github.com/python/cpython/commit/478f8291327a3e3ab17b5857699565
Changes by Brian Curtin :
--
nosy: -brian.curtin
___
Python tracker
<http://bugs.python.org/issue29553>
___
___
Python-bugs-list mailing list
Unsubscribe:
Brian Curtin added the comment:
New changeset 3d707be950b387552585451071928e7b39cdfa53 by Brian Curtin (Jim
DeLaHunt) in branch 'master':
bpo-29521 Fix two minor documentation build warnings (#41)
https://github.com/python/cpython/commit/3d707be950b387552585451071928e
New submission from Brian Petersen:
First time issue reporter here. I really love PEP 487, but I'm finding the new
__init_subclass__ functionality is not playing nicely with existing abstract
class functionality.
For example, taking the Quest example given in PEP 487 but simply a
Changes by Brian Petersen :
--
components: -Library (Lib)
type: -> behavior
___
Python tracker
<http://bugs.python.org/issue29923>
___
___
Python-bugs-lis
Changes by Brian May :
--
nosy: +brian
___
Python tracker
<http://bugs.python.org/issue30181>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
Brian May added the comment:
I made an attempt at a PR. Unfortunately some of the tests appear to fail on
some environments, and the messages produced don't exactly clarify why.
--
___
Python tracker
<http://bugs.python.org/is
Brian May added the comment:
Me getting confused at the newline in the comparison output.
--
___
Python tracker
<http://bugs.python.org/issue30181>
___
___
Pytho
Brian May added the comment:
I have already created such a pull requests. It is bidirectionally linked to
this ticket.
However concerns have been raised that the automatic bot hasn't recognised that
Ben Finney has signed the CLA. Hence it appears the pull request might be
rejected.
Brian Ward added the comment:
The "should" recommendation seems like the right direction, but feels like it
needs an explanation (in case someone's trying to run some 2.7 code and is
wondering why their comparisons don't work anymore). Unfortunately, it's a
little c
Changes by Brian Ward :
--
nosy: +Brian Ward
___
Python tracker
<http://bugs.python.org/issue24896>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Brian Ward :
--
pull_requests: +1863
___
Python tracker
<http://bugs.python.org/issue24896>
___
___
Python-bugs-list mailing list
Unsubscribe:
Brian Ward added the comment:
OK, I'll look at this soon and come up with the next iteration.
--
___
Python tracker
<http://bugs.python.org/issue24896>
___
___
New submission from Brian McCutchon :
Currently, it is possible to make a basic single-threaded executor for unit
testing:
class FakeExecutor(futures.Executor):
def submit(self, f, *args, **kwargs):
future = futures.Future()
future.set_result(f(*args, **kwargs))
return future
New submission from Brian Spratke :
I apologize if this is a stupid question, but I am not very experienced
building Python, or cross compiling.
While trying to cross compile Python 3.5.7 I can run configure, and make, but
when I try to run 'make install' it throws the error posted
Change by Brian Spratke :
--
type: -> compile error
___
Python tracker
<https://bugs.python.org/issue36438>
___
___
Python-bugs-list mailing list
Unsubscrib
New submission from Brian Skinn :
In [this project](https://github.com/bskinn/stdio-mgr) of mine, I have a tox
matrix set up with Pythons from 3.3. to 3.8. I have pytest set up to run
doctest on my
[`README.rst`](https://github.com/bskinn/stdio-mgr/blob
Brian Skinn added the comment:
Karthikeyan, my apologies for the slow reply -- I posted this right before I
went to bed.
To emphasize, the change to the formatting of the string contents, by adding
the filename, I think is not problematic: I'm using ellipses to elide
everything befor
Brian Skinn added the comment:
Here is warn.py, a minimal no-dependency repro script:
```
import doctest
class Tester:
r"""Provide docstring for testing.
>>> import warnings
>>> from contextlib import redirect_stderr
>>> from
Brian Skinn added the comment:
, it seems like the problem must somehow stem from the new commit using
frame.f_code.co_filename (or the C equivalent), instead of using __file__ as
previously.
Consider this warn2.py, similar to the other but with no single quotes in the
warning message
Brian Skinn added the comment:
TBH, now that I've tweaked tox and CI just not to run the doctests on 3.8, I
don't really need this to be fixed.
This seems like such an edge case -- a doctest catching a warning with a
message containing single quotes -- it might not really be
Brian Skinn added the comment:
It looks to me like it's a standard feature of the CPython string rendering
routines, where if single and double quotes are present in any string, the
preferred rendering is enclosure with single quotes with escaped internal
single quotes.
On
Change by Brian Skinn :
--
resolution: -> not a bug
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.org/issue36695>
___
___
Brian Skinn added the comment:
Thank you for taking the time to dig into it so deeply!
--
___
Python tracker
<https://bugs.python.org/issue36695>
___
___
Pytho
New submission from Brian Skinn :
doctest requires code examples have PS1 as ">>> " and PS2 as "... " -- that is,
each is three printed characters, followed by a space:
```
$ cat ell_err.py
import doctest
class Foo:
"""Test docstring.
&
Brian Skinn added the comment:
The application of repr() (or a repr()-equivalent) appears to occur as some
part of the exec(compile(...)) call within doctest
(https://github.com/python/cpython/blob/4f5a3493b534a95fbb01d593b1ffe320db6b395e/Lib/doctest.py#L1328-L1329).
On 3.6.6, in REPL
Brian Skinn added the comment:
Well, the warning content *itself* may not get passed through the displayhook
at raise-time, in the process of being run through stderr and displayed by the
REPL.
But, when you capture the warning content with redirect_stderr(sio) and then
">>>
Brian Skinn added the comment:
LOL. No special thanks necessary, that last post only turned into something
coherent (and possibly correct, it seems...) after a LOT of diving into the
source, fiddling with the code, and (((re-)re-)re-)writing! Believe me, it
reads as a lot more knowledgeable
Brian Skinn added the comment:
Ahh, this *will* break some doctests: any with blank PS2 lines in the 'source'
portion without the explicit trailing space:
1] >>> def foo():
2] ...print("bar")
3] ...
4] ...print("baz")
5] >>>
Brian Quinlan added the comment:
>> The current behavior is explicitly documented, so presumably
>> it can't be (easily) changed
And it isn't clear that it would be desirable to change this even if it were
possible - doing structured resource clean-up seems consi
Brian Quinlan added the comment:
If no one has short-term plans to improve multiprocessing.connection.wait, then
I'll update the docs to list this limitation, ensure that ProcessPoolExecutor
never defaults to >60 processes on windows and raises a ValueError if the user
explicitly
Change by Brian Quinlan :
--
assignee: -> bquinlan
___
Python tracker
<https://bugs.python.org/issue26903>
___
___
Python-bugs-list mailing list
Unsubscrib
Brian Quinlan added the comment:
BTW, the 61 process limit comes from:
63 - -
--
___
Python tracker
<https://bugs.python.org/issue26903>
___
___
Python-bug
Brian Quinlan added the comment:
OK, I completely disagree with my statement:
"""If you added this as an argument to shutdown() then you'd probably also have
to add it as an option to the constructors (for people using Executors as
context managers). But, if you h
Change by Brian Quinlan :
--
keywords: +patch
pull_requests: +13045
stage: needs patch -> patch review
___
Python tracker
<https://bugs.python.org/issu
Brian Quinlan added the comment:
Hey Brian, why can't you use threads in your unit tests? Are you worried about
non-determinism or resource usage? Could you make a ThreadPoolExecutor with a
single worker?
--
___
Python tracker
&
Brian Quinlan added the comment:
Can we close this bug then?
--
___
Python tracker
<https://bugs.python.org/issue26374>
___
___
Python-bugs-list mailin
Change by Brian Quinlan :
--
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.org/issue26374>
___
___
Python-bugs-list
Brian Quinlan added the comment:
Do you have a example that you could share?
I can't think of any other fakes in the standard library and I'm hesitant to be
the person who adds the first one ;-)
--
___
Python tracker
<https://bu
Brian McCutchon added the comment:
Mostly nondeterminism. It seems like creating a ThreadPoolExecutor with one
worker could still be nondeterministic, as there are two threads: the main
thread and the worker thread. It gets worse if multiple executors are needed.
Another option would be to
Brian Quinlan added the comment:
So you actually use the result of ex.submit i.e. use the resulting future?
If you don't then it might be easier to just create your own thread.
--
___
Python tracker
<https://bugs.python.org/is
Brian Quinlan added the comment:
Using a default executor could be dangerous because it could lead to deadlocks.
For example:
mylib.py
def my_func():
tsubmit(...)
tsubmit(...)
tsubmit(somelib.some_func, ...)
somelib.py
--
def some_func():
tsubmit(...) # Potential
Brian Quinlan added the comment:
Hey Ethan, I'm really sorry about dropping the ball on this. I've been burnt
out on Python stuff for the last couple of years.
When we left this, it looked like the -1s were in the majority and no one new
has jumped on to support `filter`.
If you
Brian McCutchon added the comment:
I understand your hesitation to add a fake. Would it be better to make it
possible to subclass Executor so that a third party implementation of this can
be developed?
As for an example, here is an example of nondeterminism when using a
ThreadPoolExecutor
Brian Quinlan added the comment:
Hey Hrvoje,
I agree that #1 is the correct approach. `disown` might not be the best name -
maybe `allow_shutdown` or something. But we can bike shed about that later.
Are you interested in writing a patch
Brian Quinlan added the comment:
Hey Brian,
I understand the non-determinism. I was wondering if you had a non-theoretical
example i.e. some case where the non-determinism had impacted a real test that
you wrote?
--
___
Python tracker
<ht
Brian Quinlan added the comment:
If we supported this, aren't we promising that we will always materialize the
iterator passed to map?
I think that we'd need a really strong use-case for this to be worth-while.
--
___
Python track
Brian Quinlan added the comment:
Do the `initializer` and `initargs` parameters deal with this use case for you?
https://docs.python.org/3/library/concurrent.futures.html#concurrent.futures.ThreadPoolExecutor
--
___
Python tracker
<ht
Brian Quinlan added the comment:
Ben, do you still think that your patch is relevant or shall we close this bug?
--
___
Python tracker
<https://bugs.python.org/issue22
Brian Quinlan added the comment:
How did the experiment go? Are people still interested in this?
--
___
Python tracker
<https://bugs.python.org/issue22
Change by Brian Quinlan :
--
assignee: -> bquinlan
___
Python tracker
<https://bugs.python.org/issue31783>
___
___
Python-bugs-list mailing list
Unsubscrib
Brian Quinlan added the comment:
Great report Steven!
I was able to reproduce this with the attached patch (just adds some sleeps and
prints) and this script:
from threading import current_thread
from concurrent.futures import ThreadPoolExecutor
from time import sleep
pool
Brian McCutchon added the comment:
No, I do not have such an example, as most of my tests try to fake the
executors.
--
___
Python tracker
<https://bugs.python.org/issue36
Brian Quinlan added the comment:
I think that ProcessPoolExecutor might have a similar race condition - but not
in exactly this code path since it would only be with the queue management
thread (which is only started once).
--
___
Python tracker
Change by Brian Quinlan :
--
pull_requests: +13087
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue31783>
___
___
Python-bugs-list mai
Brian Quinlan added the comment:
Brian, I was looking for an example where the current executor isn't sufficient
for testing i.e. a useful test that would be difficult to write with a real
executor but would be easier with a fake.
Maybe you have such an example from your
Brian Quinlan added the comment:
Was this fixed by https://github.com/python/cpython/pull/3895 ?
--
___
Python tracker
<https://bugs.python.org/issue30
Brian Quinlan added the comment:
When I first wrote and started using ThreadPoolExecutor, I had a lot of code
like this:
with ThreadPoolExecutor(max_workers=500) as e:
e.map(download, images)
I didn't expect that `images` would be a large list but, if it was, I wanted
all o
Brian Quinlan added the comment:
After playing with it for a while, https://github.com/python/cpython/pull/6375
seems reasonable to me.
It needs tests and some documentation.
Antoine, are you still -1 because of the complexity increase
Brian Quinlan added the comment:
My understanding is that tracebacks have a pretty large memory profile so I'd
rather not keep them alive. Correct me if I'm wrong about that.
--
___
Python tracker
<https://bugs.python.o
Change by Brian Quinlan :
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Brian Quinlan added the comment:
We can bike shed over the name in the PR ;-)
--
___
Python tracker
<https://bugs.python.org/issue36780>
___
___
Python-bug
New submission from Brian Curtin :
It would be helpful to clarify what the *predicate* callable will be called
with. I had to look into the source in order to figure out what it was going to
receive.
--
assignee: brian.curtin
components: Documentation
messages: 315824
nosy
Change by Brian Curtin :
--
keywords: +patch
pull_requests: +6311
stage: needs patch -> patch review
___
Python tracker
<https://bugs.python.org/issu
Change by Brian Curtin :
--
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.org/issue33371>
___
___
Pyth
Brian Sheldon added the comment:
This appears to be a duplicate of #22276
--
nosy: +brianmsheldon
___
Python tracker
<https://bugs.python.org/issue33392>
___
___
New submission from Brian Sheldon :
Given a `pathlib.Path` that contains symlinked subfolders, `Path.glob` (and
`.rglob`) do not follow symlinks. This is not consistent with `glob.glob`
which does.
For example given the following:
C:\Folder
C:\Folder\Subfolder -> D:\Subfolder
D:\Subfol
Change by Brian Sheldon :
--
type: -> behavior
___
Python tracker
<https://bugs.python.org/issue33428>
___
___
Python-bugs-list mailing list
Unsubscrib
Brian Skinn added the comment:
I second Wolfgang's recommendation to change the default back to `False`.
I started developing CLI apps &c. in Python ~4yrs ago; I dabbled briefly in
2.7, then switched firmly to Python 3. When I started, I was aimed at
supporting 3.3 to 3.5
Brian Ward added the comment:
In re.rst, the instances of "Correcsponds the" should be "Corresponds to the"
and "Doesn't have correcsponding inline flag" should be "No corresponding
inline flag."
--
nosy: +Brian Ward
_
New submission from Brian Sidebotham :
I am getting the following error when trying to compile Python 2.7.14 (and
previous 2.7 versions) on CentOS and RHEL7.
The main problem is that CONFIG_ARGS does not exist. I've included the build.
This RPATH is correct - it has to go through the RPM
Brian Sidebotham added the comment:
I'm not sure any of my emails came through to this ticket from my mail client.
I think this can be closed and filed under "not a bug".
Here are the mails I sent.:
Hi Marc-Andre,
Thanks for engaging.
I fixed RPATH and now things are buildi
New submission from Brian Kuhl :
With the trend to use REST APIs between the cloud and the IoT there is
increasing interest in Python on embedded devices. Cloud developer’s typical
release a reference REST implementation of JSON and/or Python on Linux and
leave it to the device developer to
Change by Brian Kuhl :
--
keywords: +patch
pull_requests: +4149
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue31904>
___
___
Python-
1101 - 1200 of 1992 matches
Mail list logo
