Fred L. Drake, Jr. added the comment:
It probably makes more sense to keep that PR for the maintenance branches, and
create a new branch / PR to land on master.
--
___
Python tracker
<https://bugs.python.org/issue34
Fred L. Drake, Jr. added the comment:
The existing PR can be re-targeted to merge to a maintenance branch (I'd be
inclined to merge manually, myself, but will have to check the current devguide
to make sure that's still allowed).
A new PR can be made for the non-documentation fix
Fred L. Drake, Jr. added the comment:
A PR for this would be good, and would certainly accelerate getting this
accomplished. Thanks, Cheryl!
--
nosy: +fdrake
___
Python tracker
<https://bugs.python.org/issue11
Change by Fred L. Drake, Jr. :
--
nosy: +fdrake
___
Python tracker
<https://bugs.python.org/issue33381>
___
___
Python-bugs-list mailing list
Unsubscribe:
Fred L. Drake, Jr. added the comment:
Joining the documentation for captured_stderr and captured_stdout makes
sense, as they can really use a single example, and the usage is
completely parallel.
I'd rather see captured_stdin handled separately, perhaps with some
additional comments i
Fred L. Drake, Jr. added the comment:
+1 for issue17987_4.patch
Thanks, Dmi!
--
___
Python tracker
<http://bugs.python.org/issue17987>
___
___
Python-bugs-list m
Fred L. Drake, Jr. added the comment:
I'm a little surprised that still exists.
The first version was generated manually.
--
nosy: +fdrake
___
Python tracker
<http://bugs.python.org/is
Fred L. Drake, Jr. added the comment:
Were I adding that today, I'd use a more verbose (but more standard)
format, like configparser or JSON. If any further use is going to be
made of it, that should be considered. Colon-delimited is a pretty
fragile f
Fred L. Drake, Jr. added the comment:
>From v5 of the patch:
+ A context managers that temporarily replaces the :data:`sys.stdin` /
+ :data:`sys.stdout` / :data:`sys.stderr` stream with :class:`io.StringIO`
+ object.
I'd go with singular nouns instead of trying to map across t
Changes by Fred L. Drake, Jr. :
--
nosy: +fdrake
___
Python tracker
<http://bugs.python.org/issue18501>
___
___
Python-bugs-list mailing list
Unsubscribe:
Fred L. Drake, Jr. added the comment:
Advising the reader to be aware of the security warnings in the API
documentation seems sufficient.
JSON isn't intended to support arbitrary data, and that's what this section is
discussing. Another section about data interchange with other ap
Fred L. Drake, Jr. added the comment:
When I read "... that can take almost any Python object ...", I don't think
the recommendation is about just a few types.
The Zope and ZODB communities certainly use pickle extensively, we're aware of
the security implications, and
Changes by Fred L. Drake, Jr. :
--
nosy: -fdrake
___
Python tracker
<http://bugs.python.org/issue18840>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Fred L. Drake, Jr. :
--
nosy: +fdrake
___
Python tracker
<http://bugs.python.org/issue15120>
___
___
Python-bugs-list mailing list
Unsubscribe:
Fred L. Drake, Jr. added the comment:
Better (IMO):
Wrap the meta-characters in brackets for a literal match. For example,
``'[?]'`` matches the character ``'?'``.
--
nosy: +fdrake
___
Python tracker
<http://bug
Fred L. Drake, Jr. added the comment:
I like this.
It would be especially nice if it were smart enough to split the segments after
sequences of line-ends (r'(\r?\n)+').
--
___
Python tracker
<http://bugs.python.o
Fred L. Drake, Jr. added the comment:
Not a foolish consistency; Guido ruled long ago that American spellings should
be used.
--
nosy: +fdrake
___
Python tracker
<http://bugs.python.org/issue19
Changes by Fred L. Drake, Jr. :
--
assignee: -> fdrake
___
Python tracker
<http://bugs.python.org/issue19100>
___
___
Python-bugs-list mailing list
Unsubscrib
Changes by Fred L. Drake, Jr. :
--
nosy: +fdrake
___
Python tracker
<http://bugs.python.org/issue6811>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Fred L. Drake, Jr. :
--
nosy: +fdrake
___
Python tracker
<http://bugs.python.org/issue6517>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Fred L. Drake, Jr. :
--
nosy: +fdrake
___
Python tracker
<http://bugs.python.org/issue7005>
___
___
Python-bugs-list mailing list
Unsubscribe:
Fred L. Drake, Jr. added the comment:
The test "value is not None" in line 620 (of the new version) could be
just "value" and get a little more value from less code.
I don't think I've ever run across a sample .ini-style file that used
unspecified values, though
Fred L. Drake, Jr. added the comment:
I just looked at some MySQL configuration examples, and wonder if the
guys that made that configuration-style choice were on crack.
MySQL's syntax is sufficient justification for this feature (however
abhorrent I consider it).
(I've not read
Changes by Fred L. Drake, Jr. :
--
nosy: +fdrake
___
Python tracker
<http://bugs.python.org/issue7311>
___
___
Python-bugs-list mailing list
Unsubscribe:
Fred L. Drake, Jr. added the comment:
I presume you're referring to the documentation for the xml.dom
package (as found at
http://docs.python.org/library/xml.dom.html#type-mapping) rather than
the Python <--> OMG IDL mapping (the link for which appears to have
gone stale).
I&#x
Fred L. Drake, Jr. added the comment:
On Tue, May 25, 2010 at 1:41 PM, AdamN wrote:
> Although I see that nowhere in the documentation.
It needn't be in the urlparse documentation; the RFCs on URL syntax
apply here. None of what's going on with the urlparse module is
Python spe
Fred L. Drake, Jr. added the comment:
The module is documented as supporting "Relative Uniform Resource
Locators", in which a value with a non-rooted path is supported using
simply "non/rooted/path".
See the third paragraph in the Python 2.6 documentation, starting
Fred L. Drake, Jr. added the comment:
On Tue, May 25, 2010 at 3:03 PM, AdamN wrote:
> I'm still confused about when anybody would use a relative path with a
> default scheme and no netloc but I'll leave that decision to you guys.
The strings are not pseudo-URLs, they'r
Fred L. Drake, Jr. added the comment:
+1
--
nosy: +fdrake
___
Python tracker
<http://bugs.python.org/issue8832>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Fred L. Drake, Jr. :
--
nosy: +fdrake
___
Python tracker
<http://bugs.python.org/issue8939>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Fred L. Drake, Jr. :
--
versions: +Python 3.1, Python 3.2
___
Python tracker
<http://bugs.python.org/issue3874>
___
___
Python-bugs-list mailin
Fred L. Drake, Jr. added the comment:
On Mon, Jun 21, 2010 at 11:00 PM, pengyu.ut wrote:
> Current pdf version of python documents don't have bookmarks for
> sussubsection. For example, there is no bookmark for the following
> section in python_2.6.5_reference.pdf.
This would b
Fred L. Drake, Jr. added the comment:
As part of this, we should ensure references to common timezones, like
UTC, only create references to a single instance rather than filling
memory with multiple instances.
One consequence of this is that shared instances should probably be immutable
Fred L. Drake, Jr. added the comment:
> Fred was a proponent of small pickle sizes in the past,
> so I am adding him to the nosy list.
Thanks!
I am a proponent of small pickle sizes, in cases where it
matters. I'm not convinced this is such a case.
The case for a small pick
Fred L. Drake, Jr. added the comment:
On Tue, Jul 6, 2010 at 4:33 PM, Éric Araujo wrote:
> Using “--” to explicitly signal positional arguments is most certainly
> right and standard, but people have to read about that for the first
> time somewhere. In a perfect world, that would be
New submission from Fred L. Drake, Jr. :
The json decoder doesn't pass tests when the C optimizations in the _json
module aren't available. The actual test failures appear fairly superficial,
but aren't the limit of the problems.
Empty objects are converted to empty lists i
Fred L. Drake, Jr. added the comment:
This lack of tests is an issue for Python 2.6 as well.
Issue 9233 might have been avoided were the pure-Python implementation tested.
--
nosy: +fdrake
versions: +Python 2.6
___
Python tracker
<h
Fred L. Drake, Jr. added the comment:
The attached test only fails for Python 2.7; removing Python 2.6 from this
issue.
--
___
Python tracker
<http://bugs.python.org/issue9
Fred L. Drake, Jr. added the comment:
On Tue, Jul 20, 2010 at 10:46 AM, anatoly techtonik wrote:
> I believe the correct convention is "Return timedelta...".
This is handled inconsistently in the documentation; I'm hoping the
current maintainers reinforce the "Retur
Fred L. Drake, Jr. added the comment:
On Tue, Jul 20, 2010 at 12:08 PM, anatoly techtonik
wrote:
> I've took the convention from here. I thought docs are generated from
> docstrings.
They're not, but I don't think that really matters.
Older documentation used the imperat
Fred L. Drake, Jr. added the comment:
On Wed, Jul 21, 2010 at 8:34 PM, Eric Smith wrote:
> Although why all of the methods say "string" and not "str" isn't clear to me.
> Probably historical.
Indeed; we used "string" in the docs as an informal w
Changes by Fred L. Drake, Jr. :
--
nosy: -fdrake
___
Python tracker
<http://bugs.python.org/issue9328>
___
___
Python-bugs-list mailing list
Unsubscribe:
Fred L. Drake, Jr. added the comment:
Patch looks good, but needs a test.
--
keywords: +easy
nosy: +fdrake
___
Python tracker
<http://bugs.python.org/issue9
Changes by Fred L. Drake, Jr. :
--
nosy: +tarek
___
Python tracker
<http://bugs.python.org/issue9173>
___
___
Python-bugs-list mailing list
Unsubscribe:
Fred L. Drake, Jr. added the comment:
I disagree.
The documentation should promote RawConfigParser, and note
SafeConfigParser and ConfigParser as remaining for backward
compatibility for existing software. Maintainers of legacy software
using ConfigParser should be encouraged to convert to
Fred L. Drake, Jr. added the comment:
We're in agreement; I was specifically adding weight to *not*
selecting the second optoin Łukasz Langa presented:
> 2. We deprecate ConfigParser in the code and in the documentation.
--
___
Python
Fred L. Drake, Jr. added the comment:
Rejected since this didn't make it into Python 2.7.
--
resolution: -> rejected
status: open -> closed
___
Python tracker
<http://bugs.python.o
Fred L. Drake, Jr. added the comment:
Reading from a string is certainly fairly common, though I'm pretty happy with
using an io.StringIO seems reasonable and straightforward.
I've never stumbled over the need to "read" from dictionaries as described.
Changes by Fred L. Drake, Jr. :
--
nosy: +fdrake
___
Python tracker
<http://bugs.python.org/issue5412>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Fred L. Drake, Jr. :
--
nosy: +fdrake
___
Python tracker
<http://bugs.python.org/issue9292>
___
___
Python-bugs-list mailing list
Unsubscribe:
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
201 - 300 of 301 matches
Mail list logo
