Change by Ian Good :
--
nosy: +icgood
nosy_count: 9.0 -> 10.0
pull_requests: +30142
pull_request: https://github.com/python/cpython/pull/13143
___
Python tracker
<https://bugs.python.org/issu
Ian Lee added the comment:
@ronaldoussoren - right, I agree that I think that raising the AttributeErrors
is the right thing. The part that feels like a bug to me is that the exception
is saying it is read only and yet it is not being treated it that way (even
though as you point out, the
Ian Lee added the comment:
@sobolevn - Hmm, interesting.. I tested in python 3.9 which I had available,
and I can reproduce your result, but I think it's different because you are
using a tuple. If I use a list then I see my same reported behavior in 3.9:
```python
Python 3.9.10 (main
New submission from Ian Lee :
Hi there - I admit that I don't really understand the internals here, so maybe
there is a good reason for this, but I thought it was weird when I just ran
across it.
If I create a new class `A`, and set it's `__slots`:
```python
➜ ~ docker run -it p
Ian Fisher added the comment:
I think it would also be helpful to make the examples at the top simpler/more
idiomatic, e.g. using a context manager for the connection and calling
conn.execute directly instead of spawning a cursor.
I think the information about the isolation_level parameter
Ian Fisher added the comment:
See bpo-45858 for a more limited proposal to only deprecate the default
converters.
--
___
Python tracker
<https://bugs.python.org/issue26
Ian Fisher added the comment:
See also bpo-26651 for a related proposal to deprecate the converter/adapter
infrastructure entirely.
The proposal in this bug is more limited: remove the default converters (though
I think the default adapters should stay), but continue to allow users to
New submission from Ian Fisher :
Per discussion at
https://discuss.python.org/t/fixing-sqlite-timestamp-converter-to-handle-utc-offsets/,
the default converters in SQLite3 have several bugs and are probably not worth
continuing to maintain, so I propose deprecating them and removing them in
New submission from Ian Currie :
Reproducible example:
>>> from pprint import pprint
>>> data = [["aa"],[2],[3],[4],[5]]
>>> pprint(data)
[["aa"], [2], [3], [4], [5]]
>>> pprint(data, depth=1)
[[...], [...
Ian added the comment:
I came across this and was confused by it too. I also don't understand the
justification with not having dicts to be affected by the `compact` parameter.
If the "compact form" is having separate entries or elements on one line,
instead of having each el
Change by Ian Fisher :
--
keywords: +patch
pull_requests: +27469
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/29200
___
Python tracker
<https://bugs.python.org/issu
Change by Ian Fisher :
--
nosy: +iafisher
___
Python tracker
<https://bugs.python.org/issue19065>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Ian Fisher :
--
nosy: +iafisher
___
Python tracker
<https://bugs.python.org/issue26651>
___
___
Python-bugs-list mailing list
Unsubscribe:
Ian Fisher added the comment:
Okay, I started a discussion here:
https://discuss.python.org/t/fixing-sqlite-timestamp-converter-to-handle-utc-offsets/10985
--
___
Python tracker
<https://bugs.python.org/issue45
Ian Fisher added the comment:
> Another option could be to deprecate the current behaviour and then change it
> to being timezone aware in Python 3.13.
This sounds like the simplest option.
I'd be interested in working on this myself, if you think it's something tha
Ian Fisher added the comment:
Unfortunately fixing this will have to be considered a backwards-incompatible
change, since Python doesn't allow naive and aware datetime objects to be
compared, so if sqlite3 starts returning aware datetimes, existing code might
break.
Alternatively, pe
Ian Fisher added the comment:
Substitute "UTC offset" for "time zone" in my comment above.
I have attached a minimal Python program demonstrating data loss from this bug.
--
Added file: https://bugs.python.org/file50324/timestamp.py
__
New submission from Ian Fisher :
The SQLite converter that the sqlite3 library automatically registers for
TIMESTAMP columns
(https://github.com/python/cpython/blob/main/Lib/sqlite3/dbapi2.py#L66) ignores
the time zone even if it is present and always returns a naive datetime object.
I
Ian Henderson added the comment:
Ah, you're right -- it looks like the 'objs' global is what's keeping these
objects alive. Sorry for the noise.
--
stage: -> resolved
status: open -> closed
___
Python tracker
<https
New submission from Ian Henderson :
To reproduce, copy the following code:
import gc
gc.collect()
objs = gc.get_objects()
for obj in objs:
try:
if isinstance(obj, X):
print(obj)
except NameError:
class X:
pass
def f():
x = X()
raise
Ian Good added the comment:
Julian,
That is certainly a workaround, however the behavior you are describing is
inconsistent with PEP-544 in both word and intention. From the PEP:
> To explicitly declare that a certain class implements a given protocol, it
> can be used as a regula
Ian Good added the comment:
I believe this was a deeper issue that affected all classes inheriting
Protocol, causing a TypeError on even the most basic case (see attached):
Traceback (most recent call last):
File "/.../test.py", line 14, in
MyClass()
File "/.../test.p
Change by Ian H :
--
keywords: +patch
pull_requests: +24282
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/25487
___
Python tracker
<https://bugs.python.org/issu
Ian H added the comment:
Proposed patch is in https://github.com/python/cpython/pull/25487.
--
___
Python tracker
<https://bugs.python.org/issue43895>
___
___
New submission from Ian H :
While working on another project I noticed that there's a cache of shared
object handles kept inside _PyImport_FindSharedFuncptr. See
https://github.com/python/cpython/blob/b2b6cd00c6329426fc3b34700f2e22155b44168c/Python/dynload_shlib.c#L51-L55.
It appears
New submission from Ian H :
Some of the import-related C API functions are documented as bypassing an
override to builtins.__import__. This appears to be the case, but the
documentation is incomplete in this regard. For example, PyImport_ImportModule
is implemented by calling PyImport_Import
New submission from Ian H :
Currently there's no easy way to get at the internal cache of module spec
objects for compiled extension modules. See
https://github.com/python/cpython/blob/20ac34772aa9805ccbf082e700f2b033291ff5d2/Python/import.c#L401-L415.
For example, these module spec ob
Change by Ian Norton :
--
keywords: +patch
pull_requests: +23954
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/25216
___
Python tracker
<https://bugs.python.org/issu
Ian Norton added the comment:
This may also cause https://bugs.python.org/issue35644
--
___
Python tracker
<https://bugs.python.org/issue43749>
___
___
Pytho
New submission from Ian Norton :
On windows, the venv module does not copy the correct python exe if the current
running exe (eg sys.executable) has been renamed (eg, named python3.exe)
venv will only make copies of python.exe, pythonw.exe, python_d.exe or
pythonw_d.exe.
If for example the
Change by Ian Wienand :
--
keywords: +patch
pull_requests: +23182
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/24358
___
Python tracker
<https://bugs.python.org/issu
New submission from Ian Wienand :
The dict based configuration does not mention the "class" option, and neither
the ini-file or dict sections mention the style tag.
--
components: Library (Lib)
messages: 385825
nosy: iwienand
priority: normal
severity: normal
status:
New submission from Ian Laughlin :
Recommend adding example to tarfile documentation to provide example of writing
a tarfile to stdout.
example:
files = [(file_1, filename_1), (file_2, filename_2)]
with tarfile.open(fileobj=sys.stdout.buffer, mode = 'w|gz') as tar:
for file
Ian Strawbridge added the comment:
On Ubuntu, Tk version is showing as 8.6.10
On Windows 10, Tk version is showing as 8.6.9
--
___
Python tracker
<https://bugs.python.org/issue42
Ian Strawbridge added the comment:
Further to the information I posted on Stack Overflow (referred to above)
relating to reproducing emoticon characters from Idle under Ubuntu, I have done
more testing. Based on some of the code/comments above, I tried modifications
which I hoped might
Ian M. Hoffman added the comment:
I agree with you. When I wrote "desired behavior" I intended it to mean "my
selfishly desired outcome of not loading my struct with a dangling pointer."
This issue seems to have descended into workarounds that treat the symptoms;
I&#x
Ian M. Hoffman added the comment:
You are correct.
After further review, I found an older ctypes issue #12836 which was then
enshrined in a workaround in the numpy.ndarray.ctypes interface to vanilla
ctypes.
https://numpy.org/doc/stable/reference/generated/numpy.ndarray.ctypes.html
Numpy
New submission from Ian M. Hoffman :
A description of the problem, complete example code for reproducing it, and a
work-around are available on SO at the link:
https://stackoverflow.com/questions/64083376/python-memory-corruption-after-successful-return-from-a-ctypes-foreign-function
In
Ian O'Shaughnessy added the comment:
>I don't know of any language that guarantees all garbage will be collected
>"right away". Do you?
I'm not an expert in this domain, so, no. I am however attempting to find a way
to mitigate this issue. Do you have any su
Ian O'Shaughnessy added the comment:
"Leak" was likely the wrong word.
It does appear problematic though.
The loop is using a fixed number of variables (yes, there are repeated dynamic
allocations, but they fall out of scope with each iteration), only one of these
variables
Ian O'Shaughnessy added the comment:
For a long running process (greatly exceeding a million iterations) the
uncollected garbage will become too large for the system (many gigabytes). A
manual execution of the gc would be required.
That seems flawed given that Python is a garbage coll
New submission from Ian O'Shaughnessy :
Using a script that has two classes A and B which contain a circular reference
variable, it is possible to cause a memory leak that is not captured by default
gc collection. Only by running gc.collect() manually do the circular references
get coll
Ian Jacob Bertolacci added the comment:
What's being done about this?
I would say this is less "misleading documentation" and more "incorrect
implementation"
There is also not an obvious temporary work-around.
--
nosy: +IanBertolacci
_
New submission from Ian Norton :
When building on HP-UX using:
The configure stage fails to detect chroot(). This is due to setting
_XOPEN_SOURCE to a value higher than 500.
The fix for this is to not set _XOPEN_SOURCE when configuring for HP-UX
--
components: Interpreter Core
New submission from Ian Jackson :
The section "Fancier Output Formatting" has the example below. This will
remind many UK readers of the 2016 EU referendum. About half of those readers
will be quite annoyed.
This annoyance seems entirely avoidable; a different example which did
New submission from Ian Carr-de Avelon :
I can't understand why the result of changes() in the example file changes. I
get:
[[6.90642211e-310]
[1.01702662e-316]
[1.58101007e-322]]
[[0.]
[0.]
[0.]]
with an Ubuntu 14 system that has had a lot of changes made. I've checked the
sa
Ian Good added the comment:
#36889 was reverted, so this is not resolved.
I'm guessing this needs to be moved to 3.9 now too. Is my original PR worth
revisiting? https://github.com/python/cpython/pull/13143/files
--
resolution: fixed ->
status: closed
Ian added the comment:
I'm sorry, I should've thought to check my python version. I was on 3.6.3 which
it would not be deleted, updated to 3.6.8 and it works as intended.
--
resolution: -> not a bug
stage: -> resolved
status: open -> closed
ver
New submission from Ian :
The documentation found here
https://docs.python.org/3.7/library/tempfile.html#tempfile.TemporaryDirectory
states the following
"On completion of the context or destruction of the temporary directory object
the newly created temporary directory and all its con
Change by Ian Good :
--
nosy: +icgood
___
Python tracker
<https://bugs.python.org/issue36889>
___
___
Python-bugs-list mailing list
Unsubscribe:
Ian Good added the comment:
I added start_tls() to StreamWriter. My implementation returns a new
StreamWriter that should be used from then on, but it could be adapted to
modify the current writer in-place (let me know).
I've added docs, an integration test, and done some additional
Change by Ian Good :
--
keywords: +patch
pull_requests: +13056
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue34975>
___
___
Python-
New submission from Ian Liu Rodrigues :
Some FTP clients will not allow changing to a directory if the path does not
ends with a slash. For example, try out this in a public FTP:
from ftplib import FTP
ftp = FTP('ftp.unicamp.br')
ftp.login()
ftp.cwd('pub/libreoffice') #
New submission from Ian Good :
There does not seem to be a public API for replacing the transport of the
StreamReader / StreamWriter provided to the callback of a call to
asyncio.start_server().
The only way I have found to use the new SSL transport is to update protected
members of the
Change by Ian Remmel :
--
title: netrc parding is overly strict -> netrc parsing is overly strict
___
Python tracker
<https://bugs.python.org/issue34908>
___
_
Ian Remmel added the comment:
Yea, somehow, I suspected it was because there's no formal spec :)
I guess technically it's an enhancement, but given that configuration dictated
by third-parties can break the environment, it does feel like a bug.
For example, I can't use
New submission from Ian Remmel :
This started as a bug report for httpie
https://github.com/jakubroztocil/httpie/issues/717#issuecomment-426125261
And became a bug report for requests
https://github.com/requests/requests/issues/4813
> But turned out to be an issue with Python's netr
New submission from Ian Burgwin :
On Python 3.7.0a4 and later (including 3.7.0b4), find_library currently always
returns None on macOS. It works on 3.7.0a3 and earlier. Tested on macOS 10.11
and 10.13.
Expected result: Tested on 3.6.5, 3.7.0a1 and 3.7.0a3:
>>> from ctypes.ut
New submission from Ian Craggs :
Using cgi.FieldStorage in an HTTP server in a subclass of
BaseHTTPRequestHandler, parsing the request with:
form = cgi.FieldStorage(fp=self.rfile,
headers=self.headers,
environ={"REQUEST_METHOD"
New submission from Ian Wienand:
Using 3.5.2-2ubuntu0~16.04.3 (Xenial) we see an occasional segfault during
garbage collection of a generator object
A full backtrace is attached, but the crash appears to be triggered inside
gen_traverse during gc
---
(gdb) info args
gen = 0x7f22385f0150
Changes by Ian Wienand :
Added file: https://bugs.python.org/file47135/crash-py-bt.txt
___
Python tracker
<https://bugs.python.org/issue31426>
___
___
Python-bugs-list m
Ian added the comment:
As indicated earlier, I would prefer to see clear instructions on how to call a
class's static method from another static method within the same class.
Currently, it's only clear how to call from outside the class.
If that's not going to happen, then I
Ian added the comment:
I would hope that the docs would cater to people who aren't sure how the
language works (and who want to confirm that they are using proper patterns).
If people already know how the language works, they won't need the docs.
Whether or not you refer to Java an
Ian added the comment:
I agree that the use case is probably rare.
I agree that to someone intimately familiar with the "self-consistent rules" of
Python, the correctness of the C.f() approach is probably obvious.
However, your documentation says:
Static methods in Python are
Ian Cordasco added the comment:
So I see the argument on both sides of this discussion. Having those optional
arguments for all the functions seems like an obvious blocker. If a submodule
is a blocker, what if we provide a context-manager to signal this?
--
nosy: +icordasc
New submission from Ian Kelling:
https://docs.python.org/3.7/library/pdb.html:
"The typical usage to break into the debugger from a running program is to
insert
import pdb; pdb.set_trace()
at the location you want to break into the debugger."
A plain read of this says: insert c
Ian Cordasco added the comment:
Why did you remove Python 3.3? It's still affected by this behaviour.
--
___
Python tracker
<http://bugs.python.org/is
New submission from Ian Cordasco:
In trying to add support for multiprocessing on Windows in Flake8, I found that
the behaviour of the module is significantly different than on Unix. If you
have a class that has class-level attributes on Unix, and you change them, put
the class into a Queue
Changes by Ian Cordasco :
--
nosy: +icordasc
___
Python tracker
<http://bugs.python.org/issue27568>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Ian Lee :
Added file: http://bugs.python.org/file43296/issue-27187-patch3.txt
___
Python tracker
<http://bugs.python.org/issue27187>
___
___
Python-bugs-list m
Ian Lee added the comment:
Good catch.
I'm uploading a new patch that addresses ``from __future__`` imports issue
explicitly.
--
___
Python tracker
<http://bugs.python.org/is
New submission from Ian Lee:
Noticed a couple methods in the text that aren't backtick quoted.
--
assignee: docs@python
components: Documentation
files: rst-formatting.txt
messages: 267015
nosy: IanLee1521, barry, docs@python
priority: normal
severity: normal
status: open
title
Ian Lee added the comment:
I added a comment on a pull request related to this that shows some of the
cases that we probably don't want to allow:
https://github.com/PyCQA/pycodestyle/pull/523#issuecomment-223464775
--
___
Python tracker
Ian Lee added the comment:
Are there any other concerns with the patch that I would be able to clean up?
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue23
Changes by Ian Lee :
Added file: http://bugs.python.org/file43134/issue-27187-patch2.txt
___
Python tracker
<http://bugs.python.org/issue27187>
___
___
Python-bugs-list m
Ian Lee added the comment:
I might also suggest that the entire "Version bookkeeping" section could be
removed in this case, as it would be covered by my newly added dunder section.
--
___
Python tracker
<http://bugs.python.o
Ian Lee added the comment:
I think that it should be updated to specify that all dunders ('__all__',
'__version__', '__author__', etc) should be placed after the module docstring
and before any imports. See issue-27187-patch1.txt for a possible update
Changes by Ian Lee :
--
nosy: +IanLee1521
___
Python tracker
<http://bugs.python.org/issue27187>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Ian Foote:
In statistics.pvariance, the sum of squares helper function (_ss) is called
twice and the first return value is unused:
https://github.com/python/cpython/blob/9043c80b0daaddb5bff1e37432d503910506727f/Lib/statistics.py#L596
--
components: Library (Lib
Ian Lee added the comment:
> Aren't there many other examples in the PEP that need to be adjusted, since
> we're changing the style not just for 'and' and 'or' but for all binary
> operators?
Admittedly I'd only looked in that one section last
Ian Lee added the comment:
Link to GitHub branch with the patch as a commit [1].
[1] https://github.com/python/peps/compare/master...IanLee1521:issue26763
--
___
Python tracker
<http://bugs.python.org/issue26
Ian Lee added the comment:
Discussion link missing from msg263453:
https://mail.python.org/pipermail/python-ideas/2016-April/039774.html
--
___
Python tracker
<http://bugs.python.org/issue26
New submission from Ian Lee:
Following up from discussion on python-ideas [1] about updating PEP-8 regarding
wrapping lines before rather than after binary operators.
--
files: wrap-before-binary-operator.patch
keywords: patch
messages: 263453
nosy: IanLee1521, gvanrossum
priority
Ian Kelly added the comment:
Chris Angelico suggested on python-list that another possibly useful thing to
do would be to add a "from __future__ import generator_stop" to
asyncio/futures.py. This would at least have the effect of causing "await
future" to raise a Run
Ian Kelly added the comment:
The place I'd expect to find it is in
https://docs.python.org/3/library/asyncio-task.html#coroutines, in the list of
"things a coroutine can do". The first two bullets in the list say that any
exceptions raised will be propagated. Maybe there s
Ian Kelly added the comment:
Fair enough. I think there should be some documentation though to the effect
that coroutines aren't robust to passing StopIteration across coroutine
boundaries. It's particularly surprising with PEP-492 coroutines, since those
aren't even iterators
Ian Kelly added the comment:
The idea is that the wrapped iterator is something potentially blocking, like a
database cursor that doesn't natively support asyncio. Usage would be something
like this:
async def get_data():
cursor.execute('select * from stuff')
a
New submission from Ian Kelly:
I was playing around with this class for adapting regular iterators to async
iterators using BaseEventLoop.run_in_executor:
import asyncio
class AsyncIteratorWrapper:
def __init__(self, iterable, loop=None, executor=None):
self._iterator = iter
Ian Kelly added the comment:
The asyncio docs also have this note, so this is technically not a bug:
Note: In this documentation, some methods are documented as coroutines, even if
they are plain Python functions returning a Future. This is intentional to have
a freedom of tweaking the
Ian Carroll added the comment:
Write still fails on 3.5.1 and OS X 10.11.2. I'm no dev, so can someone explain
how to use the patch while it's under review?
--
nosy: +Ian Carroll
___
Python tracker
<http://bugs.python.o
Ian Macartney added the comment:
I don't have much experience with what should and shouldn't be in the python
docs, however I was recently bitten by a subtlety in signal/subprocess that
might be worth documenting.
Anything written to stdout in a signal handler could end up in the s
Changes by Ian Cordasco :
--
nosy: +icordasc
___
Python tracker
<http://bugs.python.org/issue24667>
___
___
Python-bugs-list mailing list
Unsubscribe:
Ian Cordasco added the comment:
Also I'm marking this as affecting 3.3, 3.4, and 3.5. I haven't tested against
3.5, but it definitely fails on 3.4. I hope to be able to test against 3.5.0b2
tonight
--
versions: +Python 3.3, Python 3.4,
Ian Cordasco added the comment:
FWIW, the proper section to reference now is 3.2 in RFC 7230
(https://tools.ietf.org/html/rfc7230#section-3.2)
--
nosy: +icordasc
___
Python tracker
<http://bugs.python.org/issue24
Changes by Ian Cordasco :
--
nosy: +icordasc
___
Python tracker
<http://bugs.python.org/issue24107>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Ian Cordasco :
--
nosy: +icordasc
___
Python tracker
<http://bugs.python.org/issue23989>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Ian Cordasco :
--
nosy: +Lukasa
___
Python tracker
<http://bugs.python.org/issue23794>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Ian Cordasco :
--
nosy: +icordasc
___
Python tracker
<http://bugs.python.org/issue23794>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Ian Lee :
--
nosy: +IanLee1521
___
Python tracker
<http://bugs.python.org/issue23639>
___
___
Python-bugs-list mailing list
Unsubscribe:
Ian Cordasco added the comment:
So it seems like
https://rt.openssl.org/Ticket/Display.html?user=guest&pass=guest&id=3621
includes a fix that we may be able to update Python to use (safely) by default.
If we don't then this will continue to be an issue.
Other referen
1 - 100 of 190 matches
Mail list logo
