Fred L. Drake, Jr. added the comment:
2010/8/3 Łukasz Langa :
> 1) In 3.2 we add an alias:
>
> InterpolatingConfigParser = SafeConfigParser
I'd rather see the class renamed and SafeConfigParser made the alias in 3.2.
Otherwise, +1 for this plan (msg 112589), as there's
Fred L. Drake, Jr. added the comment:
Making ConfigParser an alias for SafeConfigParser creates a silent
behavioral change. An application developer may not realize that
users rely on the "full" ConfigParser anti-glory and end up breaking
their configurations without so much as p
Fred L. Drake, Jr. added the comment:
Such constructs are notoriously tedious to grep for; patches are welcome.
--
nosy: +fdrake
___
Python tracker
<http://bugs.python.org/issue9
Fred L. Drake, Jr. added the comment:
It doesn't make sense to make any of these changes to Python 2; this
really should have been separate from the documentation issue. That's
probably understood by everyone, but explicit is better.
Merging implementations
---
Fred L. Drake, Jr. added the comment:
+1 to making support for `vars` consistent across the parser classes.
This needs to include documentation (stand-alone + docstrings) that actually
make sense; the current docs require reading the code to understand what is
going on.
(Generally, if you
Fred L. Drake, Jr. added the comment:
I agree that the existing defaults={...} should never have been added to the
stdlib. It made sense in the originating application, but should have been
implemented differently to keep application-specific behavior out of what
eventually was added to the
Fred L. Drake, Jr. added the comment:
(Apparently I don't have the right permissions on Rietveld.)
- Docstrings should be written in the standard PEP-8 way (single line
summary + additional explanation as needed following a blank line).
- read_sting and read_dict should still t
Fred L. Drake, Jr. added the comment:
- Summmary lines in docstrings are one line, as Éric points out.
They're summaries, so need not be complete. Use elaboration text as
needed, and omit anything that's not relevant in context. An
alternate wording to consider:
"&qu
Fred L. Drake, Jr. added the comment:
This patch looks good to me.
--
___
Python tracker
<http://bugs.python.org/issue9292>
___
___
Python-bugs-list mailin
Fred L. Drake, Jr. added the comment:
Patch committed on py3k branch in r83889.
--
resolution: -> accepted
status: open -> closed
___
Python tracker
<http://bugs.python.org/
Fred L. Drake, Jr. added the comment:
The getters should all accept a `default` argument that's used when no value is
found in the configuration. If the default is given, that should be returned
(without conversion), instead of raising an exception.
This can be included in the same
Fred L. Drake, Jr. added the comment:
Patch still requires a test. Sorry if I was unclear in IRC.
--
___
Python tracker
<http://bugs.python.org/issue9
Fred L. Drake, Jr. added the comment:
- Using _UNSET & similar in the docs is not good; there used to be a
way to note a parameter as optional. Not sure whether there is any
more.
- Docs for methods which take vars/default should include a note
indicating where to find the explana
Fred L. Drake, Jr. added the comment:
Committed on the release27-maint branch as 83931.
--
keywords: -needs review
resolution: -> accepted
status: open -> closed
___
Python tracker
<http://bugs.python.org/
Fred L. Drake, Jr. added the comment:
Even I think the leading underscore screams "don't use this from
outside, doofus!"
--
___
Python tracker
<http://bugs.py
Fred L. Drake, Jr. added the comment:
Is there some special treatment you think should be given to specific enum
values as well?
--
nosy: +fdrake
___
Python tracker
<http://bugs.python.org/issue29
Changes by Fred L. Drake, Jr. :
--
nosy: -fdrake
___
Python tracker
<http://bugs.python.org/issue9285>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Fred L. Drake, Jr. :
--
nosy: +fdrake
___
Python tracker
<http://bugs.python.org/issue27879>
___
___
Python-bugs-list mailing list
Unsubscribe:
Fred L. Drake, Jr. added the comment:
I've read through this, but haven't applied the patch & run tests (that's what
buildbots are for).
No objections.
--
___
Python tracker
<http://bugs
Fred L. Drake, Jr. added the comment:
+1 for ValueError instead of OSError.
--
nosy: +fdrake
___
Python tracker
<http://bugs.python.org/issue23116>
___
___
Pytho
Fred L. Drake, Jr. added the comment:
As mentioned in issue 18085, the original file was not generated, but crafted
by hand (though I don't think that really matters).
--
___
Python tracker
<http://bugs.python.org/i
Fred L. Drake, Jr. added the comment:
I don't think this is a duplicate of issue 9755; this relates to verifying the
data, and that revolves around possible process improvements.
Whether this issue should be closed is tied to whether the file has been
verified, as the issue title suggest
Fred L. Drake, Jr. added the comment:
+1
It could reasonably be argued that not sorting is a bug for already-released
3.x versions.
--
___
Python tracker
<http://bugs.python.org/issue27
Changes by Fred L. Drake, Jr. :
--
nosy: +fdrake
___
Python tracker
<http://bugs.python.org/issue2175>
___
___
Python-bugs-list mailing list
Unsubscribe:
Fred L. Drake, Jr. added the comment:
Let's just update the docstring:
"""Concrete date/time and related types.
See also http://dir.yahoo.com/Reference/calendars/
For a primer on DST, including many current DST rules, see
http://webexhibits.org/daylightsaving/
Sources f
Changes by Fred L. Drake, Jr. :
--
nosy: -fdrake
___
Python tracker
<http://bugs.python.org/issue17868>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Fred L. Drake, Jr. :
--
nosy: +fdrake
___
Python tracker
<http://bugs.python.org/issue17950>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Fred L. Drake, Jr.:
The captured_stderr and captured_stdin context managers aren't documented, and
should be.
--
assignee: docs@python
components: Documentation
keywords: easy
messages: 189311
nosy: docs@python, fdrake
priority: normal
severity: normal
stage:
Changes by Fred L. Drake, Jr. :
--
resolution: -> rejected
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue17995>
___
___
Pyth
Fred L. Drake, Jr. added the comment:
Stability in output order from pprint is very useful in doctests (yes, some
people write documentation that they test).
I think fixing any output stability issues would be very worthwhile.
--
___
Python tracker
Fred L. Drake, Jr. added the comment:
Sorting by the repr sounds good, but if some dict keys or set members are
strings containing single-quotes, the primary sort will be on the type of quote
used for the repr, which would be surprising and significantly less useful
Changes by Fred L. Drake, Jr. :
--
nosy: -fdrake
___
Python tracker
<http://bugs.python.org/issue2292>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Fred L. Drake, Jr. :
--
nosy: -fdrake
___
Python tracker
<http://bugs.python.org/issue7434>
___
___
Python-bugs-list mailing list
Unsubscribe:
Fred L. Drake, Jr. added the comment:
It's not at all obvious that the intention is to ensure such an argument should
be treated only as a command external to the shell.
If an application really wants to ensure the command is not handled as a shell
built-in, it should use shell=False.
M
Changes by Fred L. Drake, Jr. :
--
nosy: +fdrake
___
Python tracker
<http://bugs.python.org/issue26094>
___
___
Python-bugs-list mailing list
Unsubscribe:
Fred L. Drake, Jr. added the comment:
On Fri, Feb 19, 2016 at 10:02 AM, Tony R. wrote:
> Holy crap! You all used to use LaTeX?! :D
Python's documentation has a long & colorful history. :-)
> Well then, if this is the sort of place where the status quo is sacred, then
>
Fred L. Drake, Jr. added the comment:
Another reason to value the status-quo in this case is that this isn't just
a matter for the Python documentation; it's about the recommended usage for
the markup, which is used by many other packages.
Questions that should be discussed include:
Fred L. Drake, Jr. added the comment:
If no one is planning to propose specific new markup for more fine-grained
version annotations, this issue can be closed.
--
___
Python tracker
<http://bugs.python.org/issue26
Fred L. Drake, Jr. added the comment:
For anyone following along only via the tracker, it's worth noting that
proposals for new markup are welcome on the docs mailing list. More
information is available at:
https://mail.python.org/mailman/listinfo
Fred L. Drake, Jr. added the comment:
The ``versionadded::`` directive should only be used to annotate descriptions
of new API entries. While it would be correctly applied to the ``Chrome`` and
``Chromium`` classes, those are not separately documented here, but are only
listed in the table
Fred L. Drake, Jr. added the comment:
Sorry; I guess I wasn't clear.
``versionadded::`` and ``versionchanged::`` are applied to specific API points
(modules, classes, methods, attributes) that are identified structurally in the
documentation. That isn't the case for this.
Whil
Fred L. Drake, Jr. added the comment:
LGTM
Thanks for getting this documented!
--
___
Python tracker
<http://bugs.python.org/issue26247>
___
___
Python-bug
Fred L. Drake, Jr. added the comment:
I see your message to python-dev, and apologize for taking so long to get to
this.
I do intend to read through your changes, and hope to be able to make time
while I'm at PyCon this coming week.
--
___
P
Fred L. Drake, Jr. added the comment:
Given that this has languished this long, patching historical releases seems
pointless.
--
status: open -> closed
___
Python tracker
<http://bugs.python.org/iss
Fred L. Drake, Jr. added the comment:
Sorry for the delay. pprint_safe_key.patch looks good to me.
--
___
Python tracker
<http://bugs.python.org/issue22
Fred L. Drake, Jr. added the comment:
I don't see any reason for proxy objects to be less hashable than ref objects.
As for the p == p case, where the referent has expired, returning True if p is
p seems acceptable (along with False inequalities, and True for other
comparisons all
Fred L. Drake, Jr. added the comment:
Clearly I've been away from this code for a long time.
The hash support for ref objects is definitely a very special case, only
intended to support WeakKeyDictionary. We that class implemented in C, we'd
probably want the hash support for refs
Fred L. Drake, Jr. added the comment:
> ref objects behave differently: they inherit their referent's hash
> value when alive, and remember it. proxy objects could be made to
> behave the same way.
They could, yes, but that would break the proxy behavior, and the hash <-->
Fred L. Drake, Jr. added the comment:
I don't recall that the issues discussed here were considered when these
classes were added; functionality was the issue at the time.
I'm not particularly opposed to adding a more data-ful repr for the
weakref-oriented mappings, but I&#x
Fred L. Drake, Jr. added the comment:
Without the star would be right. ReST does not support nested markup, and in
this case, I don't think it would make sense anyway.
--
nosy: +fdrake
___
Python tracker
<http://bugs.python.org/is
Fred L. Drake, Jr. added the comment:
"in" and "not in" are not comparisons, regardless of implementation mechanics
(which could change).
They aren't really dependent on iteration, though they often correlate with
iteration.
I'd rather see them described as &q
201 - 251 of 251 matches
Mail list logo
