Thomas Holder added the comment:
All good, thanks for opening PR 22453! I'll close my old PR.
--
___
Python tracker
<https://bugs.python.org/issue40075>
___
___
Reuben Thomas added the comment:
Thanks for the hint; could this be documented, please?
--
___
Python tracker
<https://bugs.python.org/issue41854>
___
___
Pytho
Change by Thomas Wouters :
--
nosy: +gregory.p.smith, twouters
___
Python tracker
<https://bugs.python.org/issue42443>
___
___
Python-bugs-list mailing list
Unsub
New submission from Thomas Ryschawy :
It seems to be known that in case of a Windows GUI app that isn’t connected to
a console sys.stderr can be None. See the Note on
http://docs.python.org/py3k/library/sys.html: Under some conditions stdin,
stdout and stderr as well as the original values
Changes by Thomas Ryschawy :
Removed file: http://bugs.python.org/file24263/traceback.txt
___
Python tracker
<http://bugs.python.org/issue13807>
___
___
Python-bugs-list m
Changes by Thomas Ryschawy :
Added file: http://bugs.python.org/file24264/traceback.txt
___
Python tracker
<http://bugs.python.org/issue13807>
___
___
Python-bugs-list m
Thomas Leonard added the comment:
Just to add a couple of data points to argue in favour of a secure-by-default
behaviour:
0install.net:
http://secunia.com/advisories/47935 (spoofing attack due to certificate names
not being validated)
Mozilla is recommending people avoid using Python
Thomas Atkinson added the comment:
This bug is happening in python 3.2 when trying to build pycrypto on Microsoft
Windows 7
--
nosy: +Thomas.Atkinson
versions: +Python 3.2 -Python 2.7
___
Python tracker
<http://bugs.python.org/issue2
Thomas Heller added the comment:
The rationale was to allow different packages (for example) in the same process
to have their own private instance of a foreign function, with possibly
different definitions of restype, argtypes and/or errcheck
New submission from Thomas Turner :
Problem with lstrip
>>> s = 'msgid "supplier code"'
>>>
>>> s.lstrip('msgid "')
'upplier code"'
>>>
It should come back with supplier code"
To get round the bug I
Thomas Wouters added the comment:
For the record, as I said in the review of 002.diff: LGTM.
--
___
Python tracker
<http://bugs.python.org/issue14331>
___
___
Thomas Spura added the comment:
It might be good to add some documentation to the sqlite3 module and describe
that version_info is only the PYSQLITE_VERSION and not the version of the
sqlite library.
--
nosy: +tomspur
___
Python tracker
<h
Thomas Spura added the comment:
AFAIK hg supports symlinks.
Why not just symlink .gitignore to .hgignore and keep .hgignore up to date?
But in this case "$" and "^" need to be avoided, e.g. this doesn't work for git:
Makefile$
Makefile.pre$
New submission from Thomas Wouters :
The hash randomization change conflates 'pydebug' builds (which define the
'Py_DEBUG' preprocessor symbol) and asserts (which use 'NDEBUG' instead.) While
Py_DEBUG automatically unsets NDEBUG, the inverse is not true (and shou
Thomas Hisch added the comment:
I think this tickt needs to be reopened, because
> The actual bug appears to be "doctest can't run on a module that contains
> un-unwrappable objects"
@ppperry Or do you already know where this issue is tracked?
-----
Reuben Thomas added the comment:
Just to be clear, the proposed change to the documentation is simply to add ",
*args" to the argument list of AutoNumber.__new__.
--
___
Python tracker
<https://bugs.python.o
New submission from Reuben Thomas :
By changing one line of AutoNumber:
def __new__(cls):
to
def __new__(cls, *args):
Enums derived from AutoNumber can now support constructors that take named
arguments; for example:
class Color(AutoNumber):
def __init__(self, pantone=None
Thomas Moreau added the comment:
The deadlocks I refer to in this issue are fixed by the PR #3895.
Subsequent failures (like the fact that the Executor is set in a broken state
when there is an unpickling error) are tracked in other issues so I think it is
safe to close this one
Change by Thomas Viehmann :
--
pull_requests: +13768
pull_request: https://github.com/python/cpython/pull/13894
___
Python tracker
<https://bugs.python.org/issue37
Change by Thomas Viehmann :
--
pull_requests: +13770
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/13894
___
Python tracker
<https://bugs.python.org/issu
Thomas Viehmann added the comment:
Note that the module is less granular than the filename in IPython - i.e. it's
useless for within notebooks.
--
nosy: +t-vi
___
Python tracker
<https://bugs.python.org/is
Change by Thomas Viehmann :
--
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.org/issue33826>
___
___
Pyth
Change by Thomas Viehmann :
--
nosy: -t-vi
resolution: -> rejected
___
Python tracker
<https://bugs.python.org/issue33826>
___
___
Python-bugs-list mai
New submission from Thomas Caswell :
The fix for
https://bugs.python.org/issue37213 in 3498c642f4e83f3d8e2214654c0fa8e0d51cebe5
(https://github.com/python/cpython/pull/13969) seems to break building numpy
(master) with cython (master) due to a pickle failure.
The traceback (which is mostly
Thomas Caswell added the comment:
This change also causes failures in the cython test suite (see attached).
--
Added file: https://bugs.python.org/file48422/cython_test_log.txt
___
Python tracker
<https://bugs.python.org/issue37
Thomas Caswell added the comment:
I can confirm that master branches of cpython, cython, and numpy all build
together again, thank you for the quick investigation and fix!
--
___
Python tracker
<https://bugs.python.org/issue37
New submission from Thomas Grainger :
Current behaviour
$ cat foo.py
def foo():
open('foo', 'wb')
foo()
$ python3.8 -W all::ResourceWarning -X tracemalloc=5 foo.py
foo.py:2: ResourceWarning: unclosed file <_io.BufferedWriter name='foo'>
open(
Change by Thomas Grainger :
--
title: print ResourceWarning object traceback when raise as error with -W error
-> print ResourceWarning object traceback when raised as error with -W error
and -X tracemalloc
___
Python tracker
<
Thomas Grainger added the comment:
How about assertIsPermutation?
https://www.fluentcpp.com/2019/06/25/understanding-the-implementation-of-stdis_permutation/
--
nosy: +graingert
___
Python tracker
<https://bugs.python.org/issue27
New submission from Reuben Thomas :
The CTypes documentation has this example:
>>> s = c_char_p()
>>> s.value = "abc def ghi"
>>> s.value
'abc def ghi'
>>> s.value is s.value
False
>>>
It appears not to have been updated since
New submission from Thomas Grainger :
this would allow ``warnings.catch_warnings`` to be threadsafe
--
messages: 348015
nosy: graingert
priority: normal
severity: normal
status: open
title: warnings should use a ContextVar to manage filters/registry
Thomas Grainger added the comment:
note that PEP 550 previously mentions catch_warnings as something that would
benefit from some sort of Execution Context management
> Context managers like decimal contexts, numpy.errstate, and
> warnings.catch_wa
Thomas Knox added the comment:
Any update on this? This is biting me too.
I've tested on a Raspberry Pi 3B+, a 4B and a Zero W all running buster. All of
them exhibit this same behavior.
Also, this same error is preventing Python 2.7.16 from compiling on the same
hardware.
--
Thomas Grainger added the comment:
It seems that 'viewkeys', 'viewvalues' and 'viewitems' methods were not added
to types.DictProxyType, was that intentional?
--
nosy: +graingert
___
Python tracker
<
Thomas Caswell added the comment:
https://github.com/python/cpython/pull/1236 has been merged, I believe this
issue can be closed.
--
nosy: +tcaswell
___
Python tracker
<http://bugs.python.org/issue30
New submission from Thomas Guettler:
AFAIK cls.__subclasses__() only returns the classes which the interpreter has
already loaded.
This means there can be more subclasses in modules where not imported by the
current interpreter up to now.
https://docs.python.org/3.7/library/stdtypes.html
New submission from Thomas Mortensson:
Unsure how to re-produce. Have a CoreDump file with the below backtrace. Our
module is socc, we were running a Twisted application and Python core dumped
giving us the following backtrace.
Looks like we failed to spawn a process wsing os.fork() due to a
Thomas Mortensson added the comment:
Unsure if related to:
https://bugs.python.org/issue10517
or
https://bugs.python.org/issue13156
--
___
Python tracker
<http://bugs.python.org/issue30
Thomas Mortensson added the comment:
Indeed, #29640 seems remarkably similar. Will attempt to run attached POC code.
Thank you very much for your help.
--
___
Python tracker
<http://bugs.python.org/issue30
Thomas Mortensson added the comment:
Hey, any status update on this bug? Suffered a similar issue on a Centos 6.5
kernel when spawning multiple processes in a Twisted environment. Is this PR
targeted for inclusion into the source tree?
Thanks,
Tom
--
nosy: +Thomas Mortensson
New submission from Thomas Thurman:
Currently the pydoc for tempfile.TemporaryDirectory begins
"Create and return a temporary directory."
It doesn't explain anywhere *what* it returns (in fact, it returns the name of
the directory as a string). The return type is furt
Changes by Thomas Keppler :
Added file: http://bugs.python.org/file47097/test_monotonic.py
___
Python tracker
<http://bugs.python.org/issue31267>
___
___
Python-bug
New submission from Thomas Keppler:
Hi,
I have been playing around with threading.Timer objects as timeouts for a
project and noticed that my timeouts are affected by system time changes.
To test this, I have written a small demonstration script (timer_testcase.py)
which you can find in the
New submission from Thomas Caswell:
Code to reproduce:
def import_in_finally_fail():
try:
print('yo')
finally:
import asyncio.queues as aq
Results in:
In [68]: import_in_finally
Mike Thomas added the comment:
Can this issue be reopened? As Jérémie stated, curl uses this format and
outputs cookie files using the #HttpOnly_ prefix. I also found at least one
project that is working around lack of this support:
https://code.google.com/archive/p/git-repo/
https
Thomas Caswell added the comment:
Your welcome!
Matplotlib ended up just moving the import out of the finally block once we
understood the issue.
Tom
On Tue, Aug 29, 2017 at 8:50 AM Serhiy Storchaka
wrote:
>
> Serhiy Storchaka added the comment:
>
> Thank you for your r
Thomas Dudziak added the comment:
This bug seems to be still there. I had an application fail with this same
error in inspect.getouterframes with Python 3.6.2. As far as I could trace it,
during iteration over sys.modules _tracemalloc and tracemalloc were added, not
quite sure from where
New submission from Thomas Feldmann:
When using `socketserver.StreamRequestHandler` it should be possible to specify
the newline terminator that is passed to `self.connection.makefile()`.
This would be greatly appreciated by many people who have to work with network
packets ending with `\0
New submission from Thomas Moreau:
The `ProcessPoolExecutor` processes start method can only be change by changing
the global default context with `set_start_method` at the beginning of a
script. We propose to allow passing a context argument in the constructor to
allow more flexible control
New submission from Thomas Waldmann :
See there:
https://github.com/borgbackup/borg/pull/4247
I did the first changeset after seeing some strange exception popping up which
it was handling another exception - which I assumed was related to
memoryview.release not being called in the original
Thomas Waldmann added the comment:
working, but potentially problematic because .release is not always called
(e.g. in case of an exception).
--
Added file: https://bugs.python.org/file48031/issue35686a.py
___
Python tracker
<ht
Thomas Waldmann added the comment:
with context manager, does not work.
--
Added file: https://bugs.python.org/file48032/issue35686b.py
___
Python tracker
<https://bugs.python.org/issue35
Thomas Waldmann added the comment:
with try/finally: works.
--
Added file: https://bugs.python.org/file48033/issue35686c.py
___
Python tracker
<https://bugs.python.org/issue35
Thomas Waldmann added the comment:
hmm, issue tracker does not make it easy to see which file was uploaded for
which comment, so:
a: original code, works, potentially problematic exception handling (memoryview
not always being released)
b: using the memoryview context manager, fails with
Thomas Waldmann added the comment:
I see 2 issues here:
1. I would expect that the CM approach (b) behaves equivalent to try/finally
(c), but it does not and even causes an exception.
2. The traceback given in the BufferError (in (b)) is misleading, it points to
the "print",
New submission from Thomas Krennwallner :
The `inspect` module does not contain functions for determining the current
state of asynchronous generators. That is, there is no introspection API for
asynchronous generators that match the API for generators and coroutines:
https://docs.python.org
Change by Thomas Krennwallner :
--
pull_requests: +11284
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue35759>
___
___
Python-
Change by Thomas Krennwallner :
--
pull_requests: +11284, 11285
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue35759>
___
___
Python-
Thomas Waldmann added the comment:
https://github.com/borgbackup/borg/pull/4247/files
this is the current code i have for this (it is not as simple there as in the
minimal code samples i attached here).
i meanwhile think i can not use a contextmanager there.
do you think this is as good as
New submission from Thomas Trummer :
The installer for Python 3.8.0a1 doesn't work under Windows 7. It shows the
aforementioned error message.
--
components: Installation
files: Python 3.8.0a1 (64-bit)_20190205130936.log
messages: 334865
nosy: Thomas Trummer
priority: normal
sev
Change by Thomas Trummer :
Added file: https://bugs.python.org/file48100/Python 3.8.0a1
(64-bit)_20190205131106_000_core_JustForMe.log
___
Python tracker
<https://bugs.python.org/issue35
Change by Thomas Trummer :
Added file: https://bugs.python.org/file48098/Python 3.8.0a1
(64-bit)_20190205130936_000_core_JustForMe.log
___
Python tracker
<https://bugs.python.org/issue35
Change by Thomas Trummer :
Added file: https://bugs.python.org/file48099/Python 3.8.0a1
(64-bit)_20190205131106.log
___
Python tracker
<https://bugs.python.org/issue35
Thomas Guettler added the comment:
I have the same issue on Python 2.7.12 (Ubuntu 16.04)
I tried to execute tartest.py. But I could not find a way how to create the tar
which is needed for tartest.py.
--
nosy: +guettli
___
Python tracker
<h
New submission from Thomas Knox:
Downloaded Python 3.6.1 source code onto CentOS 7.3 (64 bit), Fedora 25 (64
bit), Ubuntu 16.10 (64 bit) and Raspberry Pi 8.0 (32 bit).
Configured with
./configure --enable-shared --enable-optimizations
--enable-loadable-sqlite-extensions --disable-ipv6 --with
Thomas Knox added the comment:
I changed the configuration flags to be:
pi@pi3:~/Source/Python-3.6.1 $ ./configure --enable-optimizations
--enable-loadable-sqlite-extensions --disable-ipv6 --with-system-expat
--with-system-ffi --with-threads
The profiling filed again with:
0:04:47 [ 25/405
Thomas Knox added the comment:
The build succeeds, but the profile generation fails (only the test_asyncio
portion fails), then does a new profiled build after the profiling run
completes which succeeds.
Then, when doing a 'make install', it builds the entire thing again and run
New submission from Thomas Wouters:
There is a bit of confusion in the CPython source between Py_DEBUG and (C)
asserts. By default Python builds without Py_DEBUG and without asserts
(definining NDEBUG to disable them). Turning on Py_DEBUG also enables asserts.
However, it *is* possible to
Thomas Wouters added the comment:
Ugh, I logged in with the wrong OpenID without noticing; that was supposed to
be me ;-P
--
nosy: +twouters
___
Python tracker
<http://bugs.python.org/issue29
Changes by Thomas Wouters :
--
type: -> crash
___
Python tracker
<http://bugs.python.org/issue29942>
___
___
Python-bugs-list mailing list
Unsubscrib
New submission from Thomas Wouters:
itertools.chain.from_iterable (somewhat ironically) uses recursion to resolve
the next iterator, which means it can run out of the C stack when there's a
long run of empty iterables. This is most obvious when building with low
optimisation modes, or
Thomas Wouters added the comment:
What happens when you don't have the assert depends on whether the new function
call raises an exception or not, and keep in mind *this is what most people see
anyway*: if the new call does not raise an exception, a SystemError is raised,
with the ori
Thomas Wouters added the comment:
New changeset 5466d4af5fe76ec0a5fbc8a05675287d9e8e9d14 by T. Wouters in branch
'master':
bpo-29942: Fix the use of recursion in itertools.chain.from_iterable. (#889)
https://github.com/python/cpython/commit/5466d4af5fe76ec0a5fbc8a0567528
Thomas Wouters added the comment:
FWIW, we ran into this in real-world cases (Youtube, I think), when we switched
from using a pre-built Python interpreter to one built from source using the
same optimisation and debug levels as we use for all other C/C++ code. Even so,
the accompanying test
Changes by Thomas Wouters :
--
pull_requests: +813
___
Python tracker
<http://bugs.python.org/issue29942>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Thomas Wouters :
--
pull_requests: +812
___
Python tracker
<http://bugs.python.org/issue29942>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Thomas Wouters :
--
pull_requests: +811
___
Python tracker
<http://bugs.python.org/issue29942>
___
___
Python-bugs-list mailing list
Unsubscribe:
Thomas Wouters added the comment:
Dropped the Py_DEBUG guards from the dubious asserts in the PR.
--
___
Python tracker
<http://bugs.python.org/issue29
Thomas Wouters added the comment:
New changeset 599bb181036f724629a515317f0f39520950d51c by T. Wouters in branch
'3.6':
bpo-29942: Fix the use of recursion in itertools.chain.from_iterable. (#911)
https://github.com/python/cpython/commit/599bb181036f724629a515317f0f39
Thomas Wouters added the comment:
New changeset 9273dfe1800fc7241d69f4d523d748ebd35b3801 by T. Wouters in branch
'3.5':
bpo-29942: Fix the use of recursion in itertools.chain.from_iterable. (#912)
https://github.com/python/cpython/commit/9273dfe1800fc7241d69f4d523d748
Thomas Wouters added the comment:
New changeset d694a06206fc09b76b4507aacde5e69a248f434f by T. Wouters in branch
'2.7':
bpo-29942: Fix the use of recursion in itertools.chain.from_iterable. (#913)
https://github.com/python/cpython/commit/d694a06206fc09b76b4507aacde5e6
Changes by Thomas Wouters :
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<http://bugs.python.or
Thomas Wouters added the comment:
New changeset a00c3fd12d421e41b769debd7df717d17b0deed5 by T. Wouters in branch
'master':
bpo-29941: Assert fixes (#886)
https://github.com/python/cpython/commit/a00c3fd12d421e41b769debd7df717
Thomas Wouters added the comment:
This needs some measure of backporting, now that it's just build-time fixes.
I'll take a look.
--
___
Python tracker
<http://bugs.python.o
Changes by Thomas Wouters :
--
pull_requests: +1114
___
Python tracker
<http://bugs.python.org/issue29941>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Thomas Wouters :
--
pull_requests: +1115
___
Python tracker
<http://bugs.python.org/issue29941>
___
___
Python-bugs-list mailing list
Unsubscribe:
Thomas Wouters added the comment:
FYI, buildbot issues should be fixed by PR #930.
--
___
Python tracker
<http://bugs.python.org/issue29941>
___
___
Python-bug
Changes by Thomas Wouters :
--
pull_requests: +1118
___
Python tracker
<http://bugs.python.org/issue29941>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Thomas Wouters :
--
pull_requests: +1119
___
Python tracker
<http://bugs.python.org/issue29941>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Thomas Wouters :
--
pull_requests: +1137
___
Python tracker
<http://bugs.python.org/issue29941>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Thomas Wouters :
--
pull_requests: +1138
___
Python tracker
<http://bugs.python.org/issue29941>
___
___
Python-bugs-list mailing list
Unsubscribe:
Thomas Wouters added the comment:
New changeset 90e3518225bafaff01469ed48c472ae7db5686f0 by T. Wouters in branch
'3.6':
bpo-29941: Assert fixes (#886) (#955)
https://github.com/python/cpython/commit/90e3518225bafaff01469ed48c472a
Thomas Wouters added the comment:
New changeset 553275d125478a6563dde7523f4f28c92f1861b4 by T. Wouters in branch
'3.5':
bpo-29941: Assert fixes (#886) (#956)
https://github.com/python/cpython/commit/553275d125478a6563dde7523f4f28
Changes by Thomas Wouters :
--
pull_requests: +1153
___
Python tracker
<http://bugs.python.org/issue29941>
___
___
Python-bugs-list mailing list
Unsubscribe:
Thomas Wouters added the comment:
PR #980 adds a configure flag (--with-assertions), defaulting to the old
behaviour (no assertions by default, except when --with-pydebug is passed). I
would like to backport that to (at least) 3.6 so that we can set up a buildbot
with it, to prevent
New submission from Thomas Antony:
When inspect.isgeneratorfunction is called on the output of functools.partial,
it returns False even if the original function was a generator function. Test
case is attached.
Tested in fresh conda environment running Python 3.6.1
--
files
Changes by Thomas Antony :
--
versions: +Python 3.6
___
Python tracker
<http://bugs.python.org/issue29987>
___
___
Python-bugs-list mailing list
Unsubscribe:
Thomas Antony added the comment:
Is there any way to distinguish such callables from "normal" functions without
actually calling them?
--
___
Python tracker
<http://bugs.python.o
New submission from Thomas Moreau:
The design of ProcessPoolExecutor contains some possible race conditions that
may freeze the interpreter due to deadlocks. This is notably the case with
pickling and unpickling errors for a submitted job and returned results. This
makes it hard to reuse a
New submission from Thomas Lotze:
A csv.writer with quoting=csv.QUOTE_NONNUMERIC does not quote boolean values,
which makes a csv.reader with the same quoting behaviour fail on that value:
csv.py --
import csv
import io
f = io.StringIO()
writer = csv.writer(f, quoting
901 - 1000 of 1791 matches
Mail list logo