Chris Wilcox added the comment:
That is my thinking as well after rooting around a bit. I unfortunately am not
knowledgable enough here to be 100% sure it is complete.
--
___
Python tracker
<https://bugs.python.org/issue14
Chris Wilcox added the comment:
Thanks Eric. That is very handy.
I had made a test case earlier on a branch. Attached as a patch here if helpful.
I haven't tried to fix this yet, but would be interested if it is something
that makes sense to address.
--
keywords: +patch
Added
Chris Wilcox added the comment:
Double curly braces do not indicate to not process the inner content. They
indicate to include a literal curly brace. That said, I think there may be
something not quite correct.
I came up with an example based on the example in the format specifiers section
Chris Wilcox added the comment:
Are you still working on this Ajay Mahato?
--
nosy: +crwilcox
___
Python tracker
<https://bugs.python.org/issue9305>
___
___
Chris Wilcox added the comment:
What work remains to be done for this issue?
--
nosy: +crwilcox
___
Python tracker
<https://bugs.python.org/issue14678>
___
___
Chris Wilcox added the comment:
The attached code implements `__format__` on the `Collections` class. In case
1, the template passed to `__format__` is "{v.name}: {v.email}|". In case 2, a
name error will occur while processing the f string and v will not be found as
no object
Chris Wilcox added the comment:
I looked a bit at _strptime.py and the corresponding tests and thought I would
share my notes.
The regular expressions clearly allow non-zero padded values for both %d and %m
matches. There is one test where the following is run: time.strptime("Mar 1&q
Chris Wilcox added the comment:
As %m and %d denote zero padded forms of month and day it seems to me this
shouldn't match. Executing a small c program `char* ret = strptime("181223",
"%Y%m%d", &tm);` confirms that this is considered invalid to c. The dat
Chris Wilcox added the comment:
I may be wrong, but this seems like it could be an issue with NumPy. There are
similar issues on their GitHub around crashes on astype. It probably wouldn't
hurt to file this over there as well.
https://github.com/numpy/numpy/issues
--
nosy: +crw
Changes by Chris Wilcox :
--
pull_requests: +3312
___
Python tracker
<http://bugs.python.org/issue30581>
___
___
Python-bugs-list mailing list
Unsubscribe:
Chris Wilcox added the comment:
I was reviewing the docs for the os module and cpu_count should always return
the number of cpus on the system, not the usable CPUs. GetMaximumProcessorCount
returns a simulated count in WoW64. I have reached back out to the Windows API
dev and will see if
Chris Wilcox added the comment:
I am going to work on this if no one else has started.
--
nosy: +crwilcox
___
Python tracker
<http://bugs.python.org/issue30
New submission from Chris Wilcox:
This is a documentation change to make it easier to discover that XP is not a
supported OS. Content was taken from the 'whats new' section and added to the
top of the main article.
--
assignee: docs@python
components: Documentation
13 matches
Mail list logo