Change by Jeffrey Kintscher :
--
nosy: +Jeffrey.Kintscher
___
Python tracker
<https://bugs.python.org/issue41357>
___
___
Python-bugs-list mailing list
Unsub
Jeffrey Kintscher added the comment:
I uploaded a script illustrating the differences between how Path.resolve(),
os.path.abspath(), and os.path.realpath() handle symlinks. As noted by
Jendrik, Path.resolve() and os.path.realpath() both resolve symlinks, while
os.path.abspath() does not
Change by Jeffrey Kintscher :
--
keywords: +patch
pull_requests: +20735
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/21596
___
Python tracker
<https://bugs.python.org/issu
Change by Jeffrey Kintscher :
--
nosy: +Jeffrey.Kintscher
___
Python tracker
<https://bugs.python.org/issue41368>
___
___
Python-bugs-list mailing list
Unsub
Change by Jeffrey Kintscher :
--
nosy: +Jeffrey.Kintscher
___
Python tracker
<https://bugs.python.org/issue37095>
___
___
Python-bugs-list mailing list
Unsub
Change by Jeffrey Kintscher :
--
nosy: +Jeffrey.Kintscher
___
Python tracker
<https://bugs.python.org/issue41350>
___
___
Python-bugs-list mailing list
Unsub
Jeffrey Kintscher added the comment:
It looks like a copy of the zip_file object is getting created, probably by the
Path constructor:
zip_path = Path(zip_file, "file-a")
When return is invoked, the copy still has a reference to the now closed
bytes_io object which
Jeffrey Kintscher added the comment:
I created a simpler test case that exercises the buggy code. The problem can
be reproduced by passing ZipFile.__init__() a file-like object with the write
flag (mode "w") and then closing the file-like object before calling
ZipFile.clo
Change by Jeffrey Kintscher :
--
versions: +Python 3.10
___
Python tracker
<https://bugs.python.org/issue41350>
___
___
Python-bugs-list mailing list
Unsub
Change by Jeffrey Kintscher :
--
keywords: +patch
pull_requests: +20745
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/21604
___
Python tracker
<https://bugs.python.org/issu
Change by Jeffrey Kintscher :
--
nosy: +Jeffrey.Kintscher
___
Python tracker
<https://bugs.python.org/issue41491>
___
___
Python-bugs-list mailing list
Unsub
Change by Jeffrey Kintscher :
--
nosy: +Jeffrey.Kintscher
___
Python tracker
<https://bugs.python.org/issue41489>
___
___
Python-bugs-list mailing list
Unsub
Change by Jeffrey Kintscher :
--
nosy: +Jeffrey.Kintscher
___
Python tracker
<https://bugs.python.org/issue41477>
___
___
Python-bugs-list mailing list
Unsub
Change by Jeffrey Kintscher :
--
nosy: +Jeffrey.Kintscher
___
Python tracker
<https://bugs.python.org/issue41470>
___
___
Python-bugs-list mailing list
Unsub
Change by Jeffrey Kintscher :
--
nosy: +Jeffrey.Kintscher
___
Python tracker
<https://bugs.python.org/issue41398>
___
___
Python-bugs-list mailing list
Unsub
Change by Jeffrey Kintscher :
--
nosy: +Jeffrey.Kintscher
___
Python tracker
<https://bugs.python.org/issue41465>
___
___
Python-bugs-list mailing list
Unsub
Jeffrey Kintscher added the comment:
I looked at the implementation in Lib/_pyio.py. The only way to change the
error handler is by calling TextIOWrapper.reconfigure() and supply the new
error handler as the "errors" parameter. For example:
>>> import io
>&
Change by Jeffrey Kintscher :
--
nosy: +Jeffrey.Kintscher
___
Python tracker
<https://bugs.python.org/issue41458>
___
___
Python-bugs-list mailing list
Unsub
Change by Jeffrey Kintscher :
--
nosy: +Jeffrey.Kintscher
___
Python tracker
<https://bugs.python.org/issue41450>
___
___
Python-bugs-list mailing list
Unsub
Change by Jeffrey Kintscher :
--
nosy: +Jeffrey.Kintscher
___
Python tracker
<https://bugs.python.org/issue41456>
___
___
Python-bugs-list mailing list
Unsub
Jeffrey Kintscher added the comment:
SilentGhost's analysis is correct. The provided example code causes the error
because it is trying to move the symlink into its target when the target is a
directory. Any cross-device moving issues are unrelated to this example code.
Here i
Change by Jeffrey Kintscher :
--
versions: +Python 3.10, Python 3.7, Python 3.8, Python 3.9
___
Python tracker
<https://bugs.python.org/issue26791>
___
___
Pytho
Change by Jeffrey Kintscher :
--
nosy: -Jeffrey.Kintscher
___
Python tracker
<https://bugs.python.org/issue22107>
___
___
Python-bugs-list mailing list
Unsub
Change by Jeffrey Kintscher :
--
nosy: -Jeffrey.Kintscher
___
Python tracker
<https://bugs.python.org/issue41456>
___
___
Python-bugs-list mailing list
Unsub
Change by Jeffrey Kintscher :
--
keywords: +patch
pull_requests: +20904
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/21759
___
Python tracker
<https://bugs.python.org/issu
Change by Jeffrey Kintscher :
--
nosy: +Jeffrey.Kintscher
___
Python tracker
<https://bugs.python.org/issue41419>
___
___
Python-bugs-list mailing list
Unsub
Change by Jeffrey Kintscher :
--
nosy: +Jeffrey.Kintscher
___
Python tracker
<https://bugs.python.org/issue41238>
___
___
Python-bugs-list mailing list
Unsub
Change by Jeffrey Kintscher :
--
nosy: +Jeffrey.Kintscher
___
Python tracker
<https://bugs.python.org/issue37724>
___
___
Python-bugs-list mailing list
Unsub
Change by Jeffrey Kintscher :
--
nosy: +Jeffrey.Kintscher
___
Python tracker
<https://bugs.python.org/issue41169>
___
___
Python-bugs-list mailing list
Unsub
Change by Jeffrey Kintscher :
--
nosy: +Jeffrey.Kintscher
___
Python tracker
<https://bugs.python.org/issue41157>
___
___
Python-bugs-list mailing list
Unsub
Change by Jeffrey Kintscher :
--
nosy: +Jeffrey.Kintscher
___
Python tracker
<https://bugs.python.org/issue41168>
___
___
Python-bugs-list mailing list
Unsub
Jeffrey Kintscher added the comment:
Can you attach the Python source code for the PoC?
--
___
Python tracker
<https://bugs.python.org/issue41168>
___
___
Pytho
Change by Jeffrey Kintscher :
--
nosy: -Jeffrey.Kintscher
___
Python tracker
<https://bugs.python.org/issue41419>
___
___
Python-bugs-list mailing list
Unsub
Change by Jeffrey Kintscher :
--
nosy: +Jeffrey.Kintscher
___
Python tracker
<https://bugs.python.org/issue37495>
___
___
Python-bugs-list mailing list
Unsub
Change by Jeffrey Kintscher :
--
nosy: +Jeffrey.Kintscher
___
Python tracker
<https://bugs.python.org/issue34360>
___
___
Python-bugs-list mailing list
Unsub
Change by Jeffrey Kintscher :
--
nosy: +Jeffrey.Kintscher
___
Python tracker
<https://bugs.python.org/issue5141>
___
___
Python-bugs-list mailing list
Unsub
Change by Jeffrey Kintscher :
--
nosy: +Jeffrey.Kintscher
___
Python tracker
<https://bugs.python.org/issue41109>
___
___
Python-bugs-list mailing list
Unsub
Jeffrey Kintscher added the comment:
The workaround is to override _init(), which I agree is not desirable.
This is the relevant code in PurePath, which is the super class of
PurePosixPath:
@classmethod
def _from_parsed_parts(cls, drv, root, parts, init=True):
self = object
Jeffrey Kintscher added the comment:
Clarification:
PurePath.__new__() calls PurePath._from_parts(), which then calls
PurePath._init()
--
___
Python tracker
<https://bugs.python.org/issue41
Change by Jeffrey Kintscher :
--
nosy: +Jeffrey.Kintscher
___
Python tracker
<https://bugs.python.org/issue32884>
___
___
Python-bugs-list mailing list
Unsub
Jeffrey Kintscher added the comment:
This is easy to implement for Windows (as shown), but the unix implementation
uses io.TextIOWrapper.readline() to get the password input. The unix
implementation would have to be rewritten to provide the same functionality
Jeffrey Kintscher added the comment:
The error message is found in three different locations in the source code.
One is in the bytearray class, and the other two are in the BytesIO class.
They are unrelated code paths.
--
nosy: +Jeffrey.Kintscher
Jeffrey Kintscher added the comment:
>>> import io
>>> b = io.BytesIO()
>>> b.write(b'abc')
3
>>> buf = b.getbuffer()
>>> b.seek(0)
0
>>> b.write(b'?')
Traceback (most recent call last):
File "", line 1, in
Change by Jeffrey Kintscher :
--
keywords: +patch
pull_requests: +20931
stage: test needed -> patch review
pull_request: https://github.com/python/cpython/pull/21792
___
Python tracker
<https://bugs.python.org/issu
Change by Jeffrey Kintscher :
--
nosy: +Jeffrey.Kintscher
___
Python tracker
<https://bugs.python.org/issue41518>
___
___
Python-bugs-list mailing list
Unsub
Change by Jeffrey Kintscher :
--
nosy: +Jeffrey.Kintscher
___
Python tracker
<https://bugs.python.org/issue41517>
___
___
Python-bugs-list mailing list
Unsub
Jeffrey Kintscher added the comment:
The purpose of the _init() function in PurePath is to allow PurePath methods to
call the Path subclass override _init() function when initializing a Path
object.
--
___
Python tracker
<https://bugs.python.
Change by Jeffrey Kintscher :
--
nosy: -Jeffrey.Kintscher
___
Python tracker
<https://bugs.python.org/issue41518>
___
___
Python-bugs-list mailing list
Unsub
Jeffrey Kintscher added the comment:
Adding __init__() to PurePath complicates things and doesn't provide any
benefit. A subclass that calls super.__init__() ends up invoking
object.__init__(), which is perfectly fine.
I was able to find a solution by calling type(self)() inste
Jeffrey Kintscher added the comment:
The current implementation calls object.__new__(cls), where cls is the child
class type, from within a class method (@classmethod). This is fine for
Path.__new__() and PurePath.__new__(), which are called by the child class's
__new__(), because we
Change by Jeffrey Kintscher :
--
nosy: +Jeffrey.Kintscher
___
Python tracker
<https://bugs.python.org/issue41553>
___
___
Python-bugs-list mailing list
Unsub
Change by Jeffrey Kintscher :
--
nosy: +Jeffrey.Kintscher
___
Python tracker
<https://bugs.python.org/issue41552>
___
___
Python-bugs-list mailing list
Unsub
Change by Jeffrey Kintscher :
--
nosy: +Jeffrey.Kintscher
___
Python tracker
<https://bugs.python.org/issue35786>
___
___
Python-bugs-list mailing list
Unsub
Change by Jeffrey Kintscher :
--
keywords: +patch
pull_requests: +21034
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/21920
___
Python tracker
<https://bugs.python.org/issu
Jeffrey Kintscher added the comment:
I created a PR that should provide the desired behavior: __init__() and
__new__() get called in subclass objects that are created by Path and PurePath.
Also, Path and PurePath now have __init__() functions, and the __new__()
functions only return new
Change by Jeffrey Kintscher :
--
components: +Library (Lib)
___
Python tracker
<https://bugs.python.org/issue41109>
___
___
Python-bugs-list mailing list
Unsub
Change by Jeffrey Kintscher :
--
nosy: +Jeffrey.Kintscher
___
Python tracker
<https://bugs.python.org/issue41595>
___
___
Python-bugs-list mailing list
Unsub
Change by Jeffrey Kintscher :
--
nosy: +Jeffrey.Kintscher
___
Python tracker
<https://bugs.python.org/issue41593>
___
___
Python-bugs-list mailing list
Unsub
Change by Jeffrey Kintscher :
--
nosy: +Jeffrey.Kintscher
___
Python tracker
<https://bugs.python.org/issue41585>
___
___
Python-bugs-list mailing list
Unsub
Change by Jeffrey Kintscher :
--
nosy: +Jeffrey.Kintscher
___
Python tracker
<https://bugs.python.org/issue41560>
___
___
Python-bugs-list mailing list
Unsub
Change by Jeffrey Kintscher :
--
nosy: +Jeffrey.Kintscher
status: pending -> open
___
Python tracker
<https://bugs.python.org/issue41564>
___
___
Python-
Jeffrey Kintscher added the comment:
hex.py works for me with CPython versions 3.5, 3.7, 3.8, and 3.9, and the
master branch.
--
___
Python tracker
<https://bugs.python.org/issue41
Change by Jeffrey Kintscher :
--
keywords: +patch
pull_requests: +13285
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue18060>
___
_
Jeffrey Kintscher added the comment:
I did some testing with BSD and GNU tar to compare with Python's behavior.
jfoo:~ jeff$ tar --version
bsdtar 2.8.3 - libarchive 2.8.3
jeff@albarino:~$ tar --version
tar (GNU tar) 1.28
Both BSD tar and GNU tar can create an empty tar file that consis
Jeffrey Kintscher added the comment:
The test fails because curses.pair_content(curses.COLOR_PAIRS-1) validates its
parameter against the limits for signed short (max 32767) while
curses.COLOR_PAIRS-1 has the value 65535.
Unfortunately, re-plumbing curses.pair_content() to use signed
Jeffrey Kintscher added the comment:
I posted a bug report to the bug-ncurses mailing list:
https://lists.gnu.org/archive/html/bug-ncurses/2019-05/msg00022.html
--
___
Python tracker
<https://bugs.python.org/issue36
New submission from Jeffrey Kintscher :
ncurses 6.1 adds extended color functions to support terminals with 256 colors
(e.g. xterm-256color). The extended functions take color pair values that are
signed integers because the existing functions only take signed 16-bit values.
My goal with
Change by Jeffrey Kintscher :
--
nosy: +websurfer5
___
Python tracker
<https://bugs.python.org/issue29699>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Jeffrey Kintscher :
--
nosy: +websurfer5
___
Python tracker
<https://bugs.python.org/issue36520>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Jeffrey Kintscher :
--
nosy: +websurfer5
___
Python tracker
<https://bugs.python.org/issue36422>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Jeffrey Kintscher :
--
nosy: +websurfer5
___
Python tracker
<https://bugs.python.org/issue36372>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Jeffrey Kintscher :
--
nosy: +websurfer5
___
Python tracker
<https://bugs.python.org/issue36979>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Jeffrey Kintscher :
--
nosy: +websurfer5
___
Python tracker
<https://bugs.python.org/issue36758>
___
___
Python-bugs-list mailing list
Unsubscribe:
Jeffrey Kintscher added the comment:
A new function called curses.has_extended_color_support() will indicate whether
the linked ncurses library provides extended color support. It returns true if
curses.h defines NCURSES_EXT_COLORS and NCURSES_EXT_FUNCS, indicating that the
extended color
Jeffrey Kintscher added the comment:
Corrected typos in msg343336 for clarity:
At first glance, has_extended_colors() seems like a better name because it is
similar to has_colors(), but the two functions have very different semantics
that could confuse developers. has_extended_color_support
Jeffrey Kintscher added the comment:
I created issue #36982 to track the extended color changes since they broader
than this issue.
--
___
Python tracker
<https://bugs.python.org/issue36
Change by Jeffrey Kintscher :
--
keywords: +patch
pull_requests: +13448
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue36982>
___
_
Change by Jeffrey Kintscher :
--
type: -> enhancement
___
Python tracker
<https://bugs.python.org/issue36982>
___
___
Python-bugs-list mailing list
Unsubscrib
Change by Jeffrey Kintscher :
--
components: +Extension Modules -Library (Lib)
___
Python tracker
<https://bugs.python.org/issue36982>
___
___
Python-bugs-list m
Jeffrey Kintscher added the comment:
This explains some of the build/linkage problems encountered in issue #36630,
and that I encountered while working on issue #36982.
--
nosy: +yan12125
___
Python tracker
<https://bugs.python.org/issue36
Change by Jeffrey Kintscher :
--
keywords: +patch
pull_requests: +13487
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/13580
___
Python tracker
<https://bugs.python.org/issu
Jeffrey Kintscher added the comment:
I created pull request bpo-29699 to fix this issue. It adds an additional
exception handler to ignore FileNotFoundError for most of the try blocks that
already handle OSError.
I decided not to add it to the initial os.open() call. This should provide the
Jeffrey Kintscher added the comment:
To aid with debugging the code, the Subject line can be simplified:
>>> from email.message import EmailMessage
>>> m = EmailMessage()
>>> m['Subject'] = 'Hello
>>> =?utf-8?q?W=C3=B6rld!_Hello_W=C3=B6rl
Jeffrey Kintscher added the comment:
I uploaded a test script with some test cases:
The failure mode occurs when
1. line folding occurs
2. the first folded line has two or more words with UTF-8 characters
3. subsequent lines contain a word with UTF-8 characters located at a different
offset
Change by Jeffrey Kintscher :
--
keywords: +patch
pull_requests: +13514
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/13608
___
Python tracker
<https://bugs.python.org/issu
Change by Jeffrey Kintscher :
--
pull_requests: +13515
pull_request: https://github.com/python/cpython/pull/13610
___
Python tracker
<https://bugs.python.org/issue36
Jeffrey Kintscher added the comment:
The pull request has been submitted with both the code fix and tests.
--
___
Python tracker
<https://bugs.python.org/issue36
Jeffrey Kintscher added the comment:
I recommend closing this issue since the behavior is the same as the BSD and
GNU tar utilities.
--
type: -> behavior
___
Python tracker
<https://bugs.python.org/issu
Change by Jeffrey Kintscher :
--
type: -> behavior
___
Python tracker
<https://bugs.python.org/issue35070>
___
___
Python-bugs-list mailing list
Unsubscrib
Change by Jeffrey Kintscher :
--
nosy: +Jeffrey.Kintscher
___
Python tracker
<https://bugs.python.org/issue37040>
___
___
Python-bugs-list mailing list
Unsub
Change by Jeffrey Kintscher :
--
nosy: +Jeffrey.Kintscher
___
Python tracker
<https://bugs.python.org/issue37036>
___
___
Python-bugs-list mailing list
Unsub
Change by Jeffrey Kintscher :
Added file: https://bugs.python.org/file48369/bpo-36411.c
___
Python tracker
<https://bugs.python.org/issue36411>
___
___
Python-bugs-list m
Jeffrey Kintscher added the comment:
I adapted the test code on StackOverflow to show the expected and actual values.
I get this output using Python 2.7.16:
opening myfile with wb
writing 3 bytes to file
('f.tell(): expecting 3, got', 3)
closing myfile
opening myfile with a+
Change by Jeffrey Kintscher :
Removed file: https://bugs.python.org/file48369/bpo-36411.c
___
Python tracker
<https://bugs.python.org/issue36411>
___
___
Python-bug
Jeffrey Kintscher added the comment:
I saw the bug in the C output after I hit submit. Here is the correct output:
opening file with wb
writing 3 bytes to file
ftell(f): expecting 3, got 3
closing file
opening file with a+b
ftell(f): expecting 3, got 3
writing 3 bytes to file
ftell(f
Change by Jeffrey Kintscher :
--
nosy: +Jeffrey.Kintscher
___
Python tracker
<https://bugs.python.org/issue37005>
___
___
Python-bugs-list mailing list
Unsub
Change by Jeffrey Kintscher :
--
nosy: +Jeffrey.Kintscher
___
Python tracker
<https://bugs.python.org/issue36988>
___
___
Python-bugs-list mailing list
Unsub
Change by Jeffrey Kintscher :
--
nosy: +Jeffrey.Kintscher
___
Python tracker
<https://bugs.python.org/issue36976>
___
___
Python-bugs-list mailing list
Unsub
Change by Jeffrey Kintscher :
--
nosy: +Jeffrey.Kintscher
___
Python tracker
<https://bugs.python.org/issue36910>
___
___
Python-bugs-list mailing list
Unsub
Change by Jeffrey Kintscher :
--
nosy: +Jeffrey.Kintscher
___
Python tracker
<https://bugs.python.org/issue36881>
___
___
Python-bugs-list mailing list
Unsub
1 - 100 of 202 matches
Mail list logo