New submission from hao <359062...@qq.com>:
>From doc I see about os.statvfs "New in version 3.7: Added f_fsid.", but it
>doesn't show up when print an object os.statvfs returned. So I think maybe we
>can add the field when printing object.
--
comp
Change by hao <359062...@qq.com>:
--
keywords: +patch
pull_requests: +22397
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/23511
___
Python tracker
<https://bugs.python.or
New submission from Wen Hao :
>>>mat = [[0]*4]*4
>>> mat
[[0, 0, 0, 0], [0, 0, 0, 0], [0, 0, 0, 0], [0, 0, 0, 0]]
>>> mat[1][2]=1
>>> mat
[[0, 0, 1, 0], [0, 0, 1, 0], [0, 0, 1, 0], [0, 0, 1, 0]]
--
components: Build
messages: 389230
nosy: haowenqi.
New submission from Chenyoo Hao :
1.Formatting error due to an extra space (After the MSDN link).
2.There are extra words.
Original:
See the Unix manual page :manpage:`times(2)` and :manpage:`times(3)` manual
page on Unix or `the GetProcessTimes MSDN
<https://docs.microsoft.com/windows/wi
Change by Chenyoo Hao :
--
keywords: +patch
nosy: +Chenyoo Hao
nosy_count: 3.0 -> 4.0
pull_requests: +20232
stage: needs patch -> patch review
pull_request: https://github.com/python/cpython/pull/21055
___
Python tracker
<https://bugs.p
Change by Chenyoo Hao :
--
pull_requests: +20246
pull_request: https://github.com/python/cpython/pull/21080
___
Python tracker
<https://bugs.python.org/issue40
Change by Chenyoo Hao :
--
pull_requests: +20247
pull_request: https://github.com/python/cpython/pull/21081
___
Python tracker
<https://bugs.python.org/issue40
New submission from hao Qing:
it does have the Cursor.connection member in the pydoc result.
$ pydoc sqlite3.Cursor.connection
Help on member descriptor sqlite3.Cursor.connection in sqlite3.Cursor:
sqlite3.Cursor.connection
lines 1-3/3 (END)
but there is no document about sqlite3
New submission from Hao Huang:
When I was trying to add the same argument to both the root command and the sub
command and you put the arguments before the subcommand, In 2.7.8 the arguments
would be parsed correctly. But in 2.7.9, they wouldn't but these arguments
would show up in the
Hao Huang added the comment:
I think this patch cause the difference:
https://hg.python.org/cpython/rev/1a3143752db2
--
___
Python tracker
<http://bugs.python.org/issue24
Kang-Hao (Kenny) Lu added the comment:
Attached patch does the following beyond what the patch from haypo does:
* call the error handler
* reject 0xd800~0xdfff when decoding utf-32
The followings are on my TODO list, although this patch doesn't depend on any
of these and can be rev
Changes by Kang-Hao (Kenny) Lu :
--
nosy: +kennyluck
___
Python tracker
<http://bugs.python.org/issue7856>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Kang-Hao (Kenny) Lu :
Since Python 3.2.2 (I don't have earlier version to test with),
>>> "\udc80".encode("utf-8")
UnicodeEncodeError: *utf-8* codec can't encode character '\udc80'...
but
>>> b"\xff".dec
Changes by Kang-Hao (Kenny) Lu :
--
type: -> behavior
___
Python tracker
<http://bugs.python.org/issue13913>
___
___
Python-bugs-list mailing list
Unsubscri
New submission from Kang-Hao (Kenny) Lu :
Currently the "surrogatepass" handler always encodes the surrogates in UTF-8
and hence the behavior for, say, "\udc80".encode("latin-1",
"surrogatepass").decode("latin-1") might be unexpected and
Kang-Hao (Kenny) Lu added the comment:
> The followings are on my TODO list, although this patch doesn't depend
> on any of these and can be reviewed and landed separately:
> * make the surrogatepass error handler work for utf-16 and utf-32. (I
>should be able to fin
Kang-Hao (Kenny) Lu added the comment:
> and the table on the documentation of the codec module suggests *utf_8*
> as the name of the codec, which I believe to be equivalent to "utf_8"
> because '-' is not a valid character of an identifier.
typo: equivalent to &
Changes by Kang-Hao (Kenny) Lu :
--
nosy: +kennyluck
___
Python tracker
<http://bugs.python.org/issue12100>
___
___
Python-bugs-list mailing list
Unsubscribe:
18 matches
Mail list logo