Zbyszek Jędrzejewski-Szmek added the comment:
> I can see the need for generalized 'drive' support that sets an arbitrary
> path prefix as the 'drive'. For example, if "/var/tmp/instroot" is a 'drive',
> then joining it to "/some/p
Zbyszek Jędrzejewski-Szmek added the comment:
> It doesn't make sense to "concatenate" one absolute path to another.
Please see the original description of the issue, or Serhiy's example. I was
thinking about about a case where paths are resolved relative to a containe
New submission from Zbyszek Jędrzejewski-Szmek :
pathlib.Path.__truediv__(), i.e. pathlib.Path.joinpath() is surprising when the
second argument starts with a slash.
>>> pathlib.Path('/foo') / '/bar'
>>> PosixPath('/bar')
I know that this
Zbyszek Jędrzejewski-Szmek added the comment:
Bisect says 8a4cd700a7426341c2074a2b580306d2d60ec839 is the first bad commit.
Considering that 0x appears a few times in that patch, that seems plausible
;)
--
___
Python tracker
<ht
Zbyszek Jędrzejewski-Szmek added the comment:
Also reproduces with today's git.
--
nosy: +zbysz
___
Python tracker
<https://bugs.python.org/issue41531>
___
___
Zbyszek Jędrzejewski-Szmek added the comment:
Wow, that was quick. Thanks!
--
___
Python tracker
<https://bugs.python.org/issue41193>
___
___
Python-bugs-list m
Change by Zbyszek Jędrzejewski-Szmek :
--
nosy: +asottile
___
Python tracker
<https://bugs.python.org/issue41193>
___
___
Python-bugs-list mailing list
Unsub
New submission from Zbyszek Jędrzejewski-Szmek :
[Originally reported as https://bugzilla.redhat.com/show_bug.cgi?id=1852941.]
$ touch ~/foo
touch: cannot touch '/home/fedora/foo': Read-only file system
$ python
Python 3.9.0b3 (default, Jun 10 2020, 00:00:00)
[GCC 10.1.1 2020050
Change by Zbyszek Jędrzejewski-Szmek :
--
nosy: +zbysz
___
Python tracker
<https://bugs.python.org/issue34033>
___
___
Python-bugs-list mailing list
Unsubscribe:
Zbyszek Jędrzejewski-Szmek added the comment:
If you can import the module that defines the parser, and get at the generated
parser, this should be trivial to integrate with the build system. Something
like:
PYTHONPATH=. python3 -c 'import mymodule; p=mymodule.make_p
Changes by Zbyszek Jędrzejewski-Szmek :
--
nosy: +zbysz
___
Python tracker
<http://bugs.python.org/issue14102>
___
___
Python-bugs-list mailing list
Unsubscribe:
Zbyszek Jędrzejewski-Szmek added the comment:
Updated version (based on issue-23725.patch from rbcollins):
- move tempdir description at the end of the main section, before Examples
- do not add my name second time in ACKS
--
Added file: http://bugs.python.org/file40122/issue-23725
Zbyszek Jędrzejewski-Szmek added the comment:
I don't think tempdir should be removed. I just think it should not be used. So
what about moving the description of tempdir to the end, as it was in the last
patch, but calling the section "Other functions and
Zbyszek Jędrzejewski-Szmek added the comment:
Indeed, make distclean fixes the problem.
--
status: open -> closed
___
Python tracker
<http://bugs.python.org/issu
Zbyszek Jędrzejewski-Szmek added the comment:
Oh, for the record, the build failure:
building 'time' extension
gcc -pthread -fPIC -Wno-unused-result -Wsign-compare -Wunreachable-code
-DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes
-Werror=declaration-after-statement -I../
New submission from Zbyszek Jędrzejewski-Szmek:
I'm not sure if I'm doing something wrong, because other people should be
seeing this too... Anyway, attached patch fixes the issue for me.
--
components: Interpreter Core, Library (Lib)
files: 0001-Always-define-_Py_-_SU
Zbyszek Jędrzejewski-Szmek added the comment:
v6:
- add newline
--
Added file: http://bugs.python.org/file39112/tempfile_docs.patch
___
Python tracker
<http://bugs.python.org/issue23
Changes by Zbyszek Jędrzejewski-Szmek :
Added file: http://bugs.python.org/file39104/tempfile_docs.patch
___
Python tracker
<http://bugs.python.org/issue23725>
___
___
Zbyszek Jędrzejewski-Szmek added the comment:
Replying to review here... I get 500 server error in the patch review reply
dialogue :(
On 2015/04/15 02:40:14, r.david.murray wrote:
> http://bugs.python.org/review/23725/diff/14592/Doc/library/tempfile.rst
> File Doc/library/tempfile.rst
Zbyszek Jędrzejewski-Szmek added the comment:
Ping?
--
___
Python tracker
<http://bugs.python.org/issue23725>
___
___
Python-bugs-list mailing list
Unsubscribe:
Zbyszek Jędrzejewski-Szmek added the comment:
Actually they are not classes, so the proposed wording cannot be used. But
indeed it sounds better with the "and".
v4:
- one more "and"
--
Added file:
http://bugs.python.org/file38643/0001-docs-update-description-
Zbyszek Jędrzejewski-Szmek added the comment:
> Please start sentences with capital letters, specifically “mkstemp() and
> mkdtemp() are lower-level functions . . .”.
This would make the sentence more convoluted... I think that with markup it is
pretty clear that this is a function na
Zbyszek Jędrzejewski-Szmek added the comment:
v2:
- remove reflows
- update TemporaryDirectory description too
- do not call things which are not functions "functions"
- with O_TMPFILE the file is not unlinked, also update TemporaryFile
description for that
- link to Examples
--
New submission from Zbyszek Jędrzejewski-Szmek:
tempfile docs can use some refreshing.
--
components: Library (Lib)
files: 0001-docs-update-description-of-TemporaryFile-and-tempfil.patch
keywords: patch
messages: 238713
nosy: zbysz
priority: normal
severity: normal
status: open
title
New submission from Zbyszek Jędrzejewski-Szmek:
This is the last link on https://www.python.org/doc/versions/.
--
assignee: docs@python
components: Documentation
messages: 226457
nosy: docs@python, zbysz
priority: normal
severity: normal
status: open
title: https://docs.python.org
Zbyszek Jędrzejewski-Szmek added the comment:
Maybe a flag param for the constructor?
--
___
Python tracker
<http://bugs.python.org/issue21071>
___
___
Python-bug
New submission from Zbyszek Jędrzejewski-Szmek:
In Python 2, Struct.format used to be a str. In Python 3 it is bytes, which is
unexpected.
Why do I expect .format to be a string:
- This format is pretty much the same as a "{}-format" - plain text
- according to documentation it is c
Zbyszek Jędrzejewski-Szmek added the comment:
At least for /etc/os-release, which is slated to replace /etc/fedora-release
and other distribution specific files, the encoding in mandated to be UTF-8:
http://www.freedesktop.org/software/systemd/man/os-release.html
All strings should be in UTF
Zbyszek Jędrzejewski-Szmek added the comment:
On Fri, Mar 08, 2013 at 02:30:18PM +, Amaury Forgeot d'Arc wrote:
>
> Amaury Forgeot d'Arc added the comment:
>
> The return value for error conditions should be -1.
>
> - typeobject.c checks with "< 0&
New submission from Zbyszek Jędrzejewski-Szmek:
initproc is declared to return an int, but what returned values mean is not
documented. Noddy_init in
http://docs.python.org/3/extending/newtypes.html?highlight=initproc#adding-data-and-methods-to-the-basic-example
can be seen to return 0 on
Zbyszek Jędrzejewski-Szmek added the comment:
Thanks for noticing. Replaced patch with the ('x') -> ('x',) bugfix.
--
___
Python tracker
<http://
Changes by Zbyszek Jędrzejewski-Szmek :
Removed file: http://bugs.python.org/file27095/argparse_parse_args_tuple.diff
___
Python tracker
<http://bugs.python.org/issue15
Changes by Zbyszek Jędrzejewski-Szmek :
Added file: http://bugs.python.org/file27103/argparse_parse_args_tuple.diff
___
Python tracker
<http://bugs.python.org/issue15
Zbyszek Jędrzejewski-Szmek added the comment:
On Sun, Sep 02, 2012 at 02:42:34PM +, R. David Murray wrote:
>
> R. David Murray added the comment:
>
> I wonder if this is problematic enough that it should be treated as a
> regression and fixed in the next RC?
I believe ye
New submission from Zbyszek Jędrzejewski-Szmek:
After recent change (78307 '#13922: argparse no longer incorrectly strips '--'
after the first one.'), parse_args stopped working with a tuple
argument. It is easy to pass tuple to argparse by using positional function
arg
Zbyszek Jędrzejewski-Szmek added the comment:
A new version of the tests: one for 'python -X faulthandler', one for
'PYTHONFAULTHANDLER=1 python'. This one sets the environment properly for the
second test, but is slightly more invasive.
Both tests fail without Antoi
Zbyszek Jędrzejewski-Szmek added the comment:
% PYTHONFAULTHANDLER=1 ./python -E -c 'import faulthandler;
faulthandler._sigsegv()'
[3]14516 segmentation fault (core dumped)
Unless I'm missing something, the env. var. is not working as documented.
Patch with two tests i
Zbyszek Jędrzejewski-Szmek added the comment:
I can confirm that it works with the patch. Thanks!
--
___
Python tracker
<http://bugs.python.org/issue14
Changes by Zbyszek Jędrzejewski-Szmek :
--
title: faulthandler: segfault with "SystemError: null argument to internal
routine" -> faulthandler: fatal error with "SystemError: null argument to
internal routine"
__
New submission from Zbyszek Jędrzejewski-Szmek :
Simply running './python -X faulthandler' in the source directory gives me this:
% ./python -X faulthandler
Fatal Python error: Py_Initialize: can't initialize faulthandler
SystemError: null argument to internal routine
[1]25
40 matches
Mail list logo