Change by wim glenn :
--
nosy: +wim.glenn
nosy_count: 2.0 -> 3.0
pull_requests: +27651
pull_request: https://github.com/python/cpython/pull/29393
___
Python tracker
<https://bugs.python.org/issu
wim glenn added the comment:
added Graham Dumpleton to nosy list in case he has some useful insight here, I
think the PR from issue19072 may have been adapted from grahamd's patch
originally?
--
nosy: +grahamd
___
Python tracker
<ht
Change by wim glenn :
--
nosy: +wim.glenn
___
Python tracker
<https://bugs.python.org/issue40379>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by wim glenn :
--
nosy: +wim.glenn
___
Python tracker
<https://bugs.python.org/issue45356>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by wim glenn :
--
nosy: +wim.glenn
___
Python tracker
<https://bugs.python.org/issue27153>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by wim glenn :
--
nosy: +wim.glenn
___
Python tracker
<https://bugs.python.org/issue28742>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by wim glenn :
--
nosy: +wim.glenn
___
Python tracker
<https://bugs.python.org/issue29249>
___
___
Python-bugs-list mailing list
Unsubscribe:
wim glenn added the comment:
I was seeing this problem when building 3.6.4. Fixed it by replacing the test
cert with a newer one from 3.6.13:
curl
https://raw.githubusercontent.com/python/cpython/v3.6.13/Lib/test/keycert.pem >
./Lib/test/keycert.pem
Hope this helps someone else
wim glenn added the comment:
Oh, I've missed that part. Although the note (5) seems to indicate that the
copy method refers to sequence types which don't support slicing, it still
seems adequately documented under the mutable sequence operations.
I'll close this.
--
stage
New submission from wim glenn :
bytearray type has a copy method which seems to be undocumented
https://docs.python.org/3/library/stdtypes.html#bytes-and-bytearray-operations
--
assignee: docs@python
components: Documentation
messages: 385164
nosy: docs@python, wim.glenn
priority
Change by wim glenn :
--
nosy: +wim.glenn
nosy_count: 4.0 -> 5.0
pull_requests: +21636
pull_request: https://github.com/python/cpython/pull/22659
___
Python tracker
<https://bugs.python.org/issu
Change by wim glenn :
--
keywords: +patch
pull_requests: +21312
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/22257
___
Python tracker
<https://bugs.python.org/issu
New submission from wim glenn :
Qualifying that the right operand's type must be a *strict* subclass for the
reflected method to take precedence avoids an edge case / counter-example when
the types are actually equal.
>>> class A:
... def __add__(se
wim glenn added the comment:
Hi Raymond, any update on this?
--
nosy: +wim.glenn
___
Python tracker
<https://bugs.python.org/issue34394>
___
___
Python-bug
Change by wim glenn :
--
nosy: +wim.glenn
___
Python tracker
<https://bugs.python.org/issue17005>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from wim glenn :
https://docs.python.org/3/howto/descriptor.html
Current descriptor how-to guide, above, has no mention about API features added
since Python 3.6 (see __set_name__ in PEP 487)
It's an important and useful piece of using descriptors effectively and the
guide
Change by wim glenn :
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Change by wim glenn :
--
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.org/issue36761>
___
___
Python-bugs-list
Change by wim glenn :
--
pull_requests: +16953
pull_request: https://github.com/python/cpython/pull/17472
___
Python tracker
<https://bugs.python.org/issue27
Change by wim glenn :
--
nosy: +wim.glenn
___
Python tracker
<https://bugs.python.org/issue31542>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from wim glenn :
https://docs.python.org/3/c-api/tuple.html#c.PyTuple_GetSlice
In the c-api it says (emphasis mine):
PyObject* PyTuple_GetSlice(PyObject *p, Py_ssize_t low, Py_ssize_t high)ΒΆ
Return value: New reference.
Take a slice of the tuple pointed to by p from
wim glenn added the comment:
Raymond,
I understand that consecutive appends could potentially trigger multiple
resizes behind the scenes, and so it's not really showing that extend is more
like a bulk update as you mentioned. That's a good point!
However I think it's a more important
Change by wim glenn :
--
keywords: +patch
pull_requests: +14720
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/14951
___
Python tracker
<https://bugs.python.org/issu
New submission from wim glenn :
>From https://docs.python.org/3/tutorial/datastructures.html#more-on-lists :
list.extend(iterable)
Extend the list by appending all the items from the iterable.
Equivalent to a[len(a):] = iterable.
The "equivalent" is not very g
wim glenn added the comment:
This anchor works, by the way:
https://docs.python.org/3/library/functions.html#func-bytes
Hopefully someone more fluent in the docs syntax can figure out a way to fix
the anchor-link hovers
--
___
Python tracker
wim glenn added the comment:
https://docs.python.org/3/library/functions.html
Usually the little paragraph icon appears when you hover over a function name,
giving an anchor link. It's not doing it for bytes or bytearray.
Was that an unintended consequence of disambiguation from
New submission from wim glenn :
Section
https://docs.python.org/3/library/collections.html#ordereddict-examples-and-recipes
class LastUpdatedOrderedDict(OrderedDict):
'Store items in the order the keys were last added'
def __setitem__(self, key, value):
super
wim glenn added the comment:
Serhiy,
`a, *L[::2] = "abc"` as an alternative is interesting, thanks. The other
example `L[:], *rest = 'abcdef'` is less interesting because L[:] can be
arbitrary size.
When noticing this, I had tried to consume a generator into every other
New submission from wim glenn :
Could cases like these be made to work? *Should* cases like these be made to
work?
L = [0, 1, 2]
L[::2], *rest = "abcdef"
# ValueError: attempt to assign sequence of size 1 to extended slice of size 2
a, L[::2] = "abc"
# ValueError: too m
Change by wim glenn :
--
keywords: +patch
pull_requests: +9152
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue29636>
___
___
Python-
Change by wim glenn :
--
pull_requests: +8545
stage: commit review -> patch review
___
Python tracker
<https://bugs.python.org/issue28617>
___
___
Python-
Changes by wim glenn <wim.gl...@gmail.com>:
--
versions: +Python 3.6, Python 3.7
___
Python tracker <rep...@bugs.python.org>
<https://bugs.python
wim glenn added the comment:
+1, would like to use this feature too, and I would like it also in
pathlib.PosixPath.glob
--
nosy: +wim.glenn
___
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/i
wim glenn added the comment:
This issue also got me. compresslevel kwarg works fine for tarfile.open(...,
mode='w:gz') but raises exception for tarfile.open(..., mode='w|gz')
I want to use stream compression, and compresslevel=1 is more than enough for
my use case, the default of 9 is way
Changes by wim glenn <wim.gl...@gmail.com>:
--
pull_requests: +2040
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue30583>
___
_
Changes by wim glenn <wim.gl...@gmail.com>:
--
type: -> enhancement
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue30583>
___
__
Changes by wim glenn <wim.gl...@gmail.com>:
--
assignee: -> docs@python
components: +Documentation
nosy: +docs@python
___
Python tracker <rep...@bugs.python.org>
<http://bugs.pyt
Changes by wim glenn <wim.gl...@gmail.com>:
--
pull_requests: +2038
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue30583>
___
_
New submission from wim glenn:
Typo from
https://github.com/python/cpython/commit/94c8a3f91fbba72845706853d28bd5af8fc11875#diff-5a85d656ffad06e86bee33767ae24f33R1852
went unnoticed and is present in official docs
https://docs.python.org/3.6/library/datetime.html#tzinfo-objects
https
wim glenn added the comment:
May I ask, how to assign reviewers for CPython pull requests?
https://github.com/python/cpython/pull/1826 has been sitting there for 10 days
and the only comment was from a bot.
--
___
Python tracker <
Changes by wim glenn <wim.gl...@gmail.com>:
--
nosy: +wim.glenn
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue11874>
___
__
Changes by wim glenn <wim.gl...@gmail.com>:
--
pull_requests: +1912
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue11874>
___
_
wim glenn added the comment:
The test "test_help_non_breaking_spaces" from Zhang's commit fails on my
platform (other 1563 tests in the module all pass).
Interestingly, if running the entire test suite, it doesn't fail. It's only
when executing the test_argparse.py modul
wim glenn added the comment:
Guess there was no interest in this. I've released it on pypi instead (pip
install copyingmock).
https://github.com/wimglenn/copyingmock
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.p
wim glenn added the comment:
1 month later.. is newpatch.diff OK to merge or any further improvements
needed? thanks
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
wim glenn added the comment:
Here's a first attempt at a patch.
If it doesn't go into Lib finally, I'll just put up a CopyingMock on pypi
instead. But it seemed like the kind of feature which should just be in mock
directly rather than 3rd party, preferably.
--
keywords: +patch
New submission from wim glenn:
Would people be interested to consider adding the CopyingMock example shown in
the documentation section "coping with mutable arguments" into the mock module?
https://docs.python.org/3/library/unittest.mock-examples.html#coping-with-mutable-arguments
wim glenn added the comment:
Perhaps it's better to call a spade a spade here - if they're implemented as
comparisons, then why not document them as comparisons?
A colleague has mentioned one point that sets `in` and `not in` apart from the
other comparisons in the table: comparisons
wim glenn added the comment:
I want to add that the grammar explicitly mentions them as comparisons
https://docs.python.org/3/reference/grammar.html
And they are also listed in the comparisons section of the expressions
documentation
https://docs.python.org/3/reference
wim glenn added the comment:
Well, that wouldn't be true either. Because you can easily implement objects
which support membership tests but don't support iteration.
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
New submission from wim glenn:
Regarding
https://docs.python.org/3/library/stdtypes.html#comparisons
There is a line at the bottom claiming:
> Two more operations with the same syntactic priority, in and not in, are
> supported only by sequence types (below).
The claim is inc
New submission from wim glenn:
The [commented] code summarising this algorithm is incorrect because % has
precedence over -
Hey, no big deal it's just a comment after all, but may as well fix it up.
--
assignee: docs@python
components: Documentation, Interpreter Core
files
wim glenn added the comment:
Seems to be as documented here:
https://docs.python.org/2/library/pdb.html#debugger-commands
"No intelligence is applied to separating the commands; the input is split at
the first ;; pair, even if it is in the middle of a quoted string."
-
Changes by wim glenn <wim.gl...@gmail.com>:
--
nosy: +wim.glenn
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue26351>
___
__
wim glenn added the comment:
Well that was patched quickly, impressive turnaround on this
--
nosy: +wim.glenn
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
New submission from wim glenn:
The 2.7 glossary still incorrectly mentions instances of user-defined classes
hash equal to their id.
https://docs.python.org/2/glossary.html#term-hashable
Just a minor documentation bug that was unfortunately missed by
http://bugs.python.org/issue21782
New submission from wim glenn:
The comparisons section of the python 2 docs says:
---
https://docs.python.org/2/reference/expressions.html#comparisons
For the list and tuple types, x in y is true if and only if there exists an
index i such that x == y[i] is true.
---
But it's not strictly
Changes by wim glenn wim.gl...@gmail.com:
--
nosy: +wim.glenn
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21642
___
___
Python-bugs-list mailing
wim glenn added the comment:
The implementation suggested by the OP
def choice(self, seq):
Choose a random element from a non-empty
sequence.
idx = int(self.random() * len(seq))
try:
result = seq[idx] # raises IndexError if seq
is empty
except TypeError
wim glenn added the comment:
How about
if isinstance(seq, collections.Sequence):
# do it the usual way ..
else:
return choice(list(seq))
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1551113
New submission from wim glenn:
The docs http://docs.python.org/2/library/functions.html#all provide some
equivalent code for all builtin (and similarly for any):
def all(iterable):
for element in iterable:
if not element:
return False
return True
The behaviour
Changes by wim glenn wim.gl...@gmail.com:
--
nosy: -wim.glenn
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16697
___
___
Python-bugs-list
Changes by wim glenn wim.gl...@gmail.com:
--
nosy: -wim.glenn
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16468
___
___
Python-bugs-list
New submission from wim glenn:
Any object that supports the in operator can be passed as the choices value, so
dict objects, set objects, custom containers, etc. are all supported. (from
http://docs.python.org/dev/library/argparse.html#choices )
Actual behaviour is contradicted by the docs
64 matches
Mail list logo
