Fred added the comment:
> For subtle reasons, that would make us worse off. Tuple of constants get
> precomputed but lists of constants have to be rebuilt.
So if a list is 20 times slower than a tuple, I can still do billions of
computations in a second on a Raspberry Pi, so does it
New submission from Fred Drake :
A local time offset of '-' is not handled the same way as an offset of
'+', but I'd expect it would be:
>>> import email.utils
>>>
>>> email.utils.parsedate_to_datetime('9 Dec 2021 08:52:04 -')
datetime.dat
Fred added the comment:
Yeah, those other languages such as C# and JavaScript and others make async
much more easier, approachable, reduces boilerplate code and lowers the bar for
entry!
--
___
Python tracker
<https://bugs.python.org/issue45
Fred added the comment:
I don't care what async framework is used, nor do I care if its a x86 or ARM,
or if its Windows or Linux.
I don't want to have to setup an async runner because it is boilerplate code,
and it brings concern into my application which is outside of the domain of my
Fred added the comment:
$ python3 --async myscript.py
unknown option --async
Also I cannot go around telling other people how to run my script. My script
must be able to run properly without any special setup.
--
___
Python tracker
<ht
Fred added the comment:
I think it would fit with the design and commmunity of Python. I think people
who use Python don't care about what async runtime it is, or how to configure
it or set it up, they just want to call async functions.
This is 2021, we live in a async-first world. I think
Fred added the comment:
No, I was not aware of that.
After I started Python by running "python3 -m asyncio" then it behaved as I
expected it should behave by default.
But this seems to work only in the REPL. I would like to write Python scripts
stored in files where I can ea
New submission from Fred :
I want top-level await without any boilerplate code or setup.
Just write a "await" statement on line 1 without any indention.
#!/usr/bin/env python3
import asyncio
await asyncio.sleep(1)
I don't want to have to call asyncio.run(main()), a
Fred added the comment:
How is this going? Any progress?
--
___
Python tracker
<https://bugs.python.org/issue40990>
___
___
Python-bugs-list mailing list
Unsub
Fred added the comment:
It could look for a existing certificate in a well-known location, and could
fallback to an self-signed certificate that could be shipped with Python.
--
nosy: +Fred
___
Python tracker
<https://bugs.python.org/issue40
New submission from Fred :
The http.server module only supports HTTP.
https://docs.python.org/3/library/http.server.html
I propose that it should also support HTTPS.
This would allow it to serve files that depend on features that are restricted
to secure contexts.
https
healthy!
Fred
Email: https://www.killetsoft.de/email.htm?lan=e=News
--
https://mail.python.org/mailman/listinfo/python-list
Fred Drake added the comment:
PR applied and backported; closing this.
Thanks, Jared!
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Fred Drake added the comment:
New changeset 455583b54aaec9a4266ff37dd438cbbd8ec6068a by Miss Islington (bot)
in branch '3.8':
bpo-43620: Remove reference to os.sep from os.path.join() doc (GH-25025,
GH-5030)
https://github.com/python/cpython/commit/455583b54aaec9a4266ff37dd438cbbd8ec6068a
Fred Drake added the comment:
New changeset f311290f091957653bba5ebfda28ad981bb78363 by Miss Islington (bot)
in branch '3.9':
bpo-43620: Remove reference to os.sep from os.path.join() doc (GH-25025)
(#25027)
https://github.com/python/cpython/commit/f311290f091957653bba5ebfda28ad981bb78363
Fred Drake added the comment:
New changeset 21a2cabb3795f5170c746ab8f29e9d25c7442550 by Jared Sutton in
branch 'master':
bpo-43620: Remove reference to os.sep from os.path.join() doc (#25025)
https://github.com/python/cpython/commit/21a2cabb3795f5170c746ab8f29e9d25c7442550
Fred Drake added the comment:
Just reviewed the documentation for both os.sep and os.path.join().
The os.sep docs do not suggest it can be set, and the reference in the
os.path.join() description is silent regarding that, so can be read as Jared
did. I don't recall this coming up before
Fred Drake added the comment:
Perhaps Jared was expecting that modifying os.sep would affect the functions in
os.path?
os.sep was never intended to be updated.
Using the specific *path modules to work with "foreign" paths has long been
advocated as the way to do this. It is
Fred Drake added the comment:
New changeset 9bdb5802361016704fb3434369741cc6c5e08f02 by Mariusz Felisiak in
branch '3.8':
bpo-43353: Document that logging.getLevelName() accepts string representation
of logging level. (GH-24693) (#24825)
https://github.com/python/cpython/commit
Fred Drake added the comment:
Mariusz: Good point. IMO, an insane API behavior, but a legacy we must live
with.
No further objections from me.
--
___
Python tracker
<https://bugs.python.org/issue43
Fred Drake added the comment:
Just noticed this fly by in the stream of emails... sorry for not commenting
earlier.
The patch seems to describe "Level #" as "numeric", which I would not be
inclined to do. It includes the numeric value since there's no available name
fo
Change by Fred Drake :
--
nosy: +fdrake
___
Python tracker
<https://bugs.python.org/issue4>
___
___
Python-bugs-list mailing list
Unsubscribe:
Fred Drake added the comment:
And that is why the original code was checking not only for the type, but the
actual __repr__ method itself.
I think the current behavior is broken.
--
___
Python tracker
<https://bugs.python.org/issue39
Fred Drake added the comment:
Ah, good find! It's been so long since the first version of that code, but the
implementation was surprisingly nuanced.
--
___
Python tracker
<https://bugs.python.org/issue39
Fred Drake added the comment:
Adding serhiy.storchaka to nosy list since it looks like he introduced the
isinstance check on purpose (see bpo-23741).
Though bpo-23741 asserts that no behavior was changed with the patch applied
then, reading through the change leads me to think this did
Fred AYERS added the comment:
I tried this one http://gtxgamer.fr/robots.txt/;>http://gtxgamer.fr/robots.txt and it
seems to work.
--
nosy: +Fred AYERS
___
Python tracker
<https://bugs.python.org/issu
Fred Drake added the comment:
The Python 2.7 documentation was not clear that xml.etree.cElementTree was
optional, so users who didn't dive into the implementation or build process
could easily not have known unless someone with a more limited installation
used their code
Fred Drake added the comment:
Same core problem (module removed with insufficient document update), but a
different action is needed for 3.8 and 3.9.
When I started testing an application with 3.9 and found one of the
dependencies broken because it was relying directly
New submission from Fred Drake :
Since xml.etree.cElementTree does not exist in Python 3.9, the statement that
it's deprecated should be removed from the documentation.
--
assignee: docs@python
components: Documentation
keywords: easy
messages: 365016
nosy: docs@python, fdrake
Change by Fred Drake :
--
keywords: +easy
___
Python tracker
<https://bugs.python.org/issue40064>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Fred Drake :
--
assignee: docs@python
components: Documentation
nosy: docs@python, fdrake
priority: normal
severity: normal
status: open
title: py38: document xml.etree.cElementTree will be removed in 3.9
versions: Python 3.8
___
Python
Change by Fred Drake :
--
nosy: +fdrake
___
Python tracker
<https://bugs.python.org/issue39480>
___
___
Python-bugs-list mailing list
Unsubscribe:
Fred Drake added the comment:
Thanks, Julien!
Sounds good to me; no reason for a PR addressing this specific issue to be held
up once one becomes available.
--
___
Python tracker
<https://bugs.python.org/issue38
Change by Fred Drake :
--
resolution: fixed -> rejected
stage: resolved ->
___
Python tracker
<https://bugs.python.org/issue38621>
___
___
Python-bugs-
Fred Drake added the comment:
It turns out this was a problem in 3.7.4; Python 3.7.5 seems to have fixed this.
Sorry for the noise.
Guess it's time to update my application to use 3.7.5!
--
resolution: -> fixed
stage: -> resolved
status: open -&g
Fred Drake added the comment:
This problem does not exist in Python 3.6 or Python 3.8; it appears to only
exist in Python 3.7.
--
versions: +Python 3.7
___
Python tracker
<https://bugs.python.org/issue38
Fred Drake added the comment:
While I don't know Felipe's use case, I would expect the documentation to be
clear that the representation won't change in the future so users will know
that this can be relied on to generate keys into some other persistent
structure.
--
nosy: +fdrake
Fred Drake added the comment:
It's worth noting that dealing with this header eventually causes the header
parser to enter an infinite loop.
--
___
Python tracker
<https://bugs.python.org/issue38
New submission from Fred Drake :
I've encountered a problem parsing an email with this Subject: header:
Subject: Be sure to redeem your =?utf-8?Q?$?=201.71 credit card reward
certificate by the end of the year
email._header_value_parser.get_unstructured defers to get_encoded_word, passing
Fred L. Drake, Jr. added the comment:
I'd like to see consistent usage by default, with specific examples using the
older forms as appropriate. The use cases Raymond identified are worth
discussing (and the tutorial may be a good place for this), and well as
mentioned in the reference docs
Fred L. Drake, Jr. added the comment:
Definitely agree with Eric on this; code modernization is definitely on the
risky side, so judicious updates are important. (Of course, not updating is
also a risk, eventually. But not much of one in this case.)
This issue is really about whether
Fred L. Drake, Jr. added the comment:
I agree that it's less invasive and easier to review.
My question (and it's just that) is whether we've made a decision to prefer one
formatting syntax over others (outside of examples discussing the formatting
approaches themselves).
If a decision
Fred L. Drake, Jr. added the comment:
Does it make sense to change just one example?
I'm not sure what the long-term stance is on whether %-formatting should be
replaced at this point, but shouldn't this be a matter of which string
formatting approach we want overall, rather than adjusting
Change by Fred L. Drake, Jr. :
--
versions: +Python 3.9
___
Python tracker
<https://bugs.python.org/issue38255>
___
___
Python-bugs-list mailing list
Unsub
Change by Fred L. Drake, Jr. :
--
versions: +Python 3.8
___
Python tracker
<https://bugs.python.org/issue38255>
___
___
Python-bugs-list mailing list
Unsub
Python 3.7.4 won’t uninstall, I have tried doing what I can such as going to
the control panel and uninstalling the program there, but that did not work.
Since I am unable to delete it I am unable to download a different version of
python. How do I fix this and fully uninstall python?
Sent
Fred L. Drake, Jr. added the comment:
Provisional status should not cause a module or other API element to be omitted
from the indexes. So long as it's marked provisional where it's described, it
should be locatable.
--
nosy: +fdrake
___
Python
Change by Fred L. Drake, Jr. :
--
nosy: +fdrake
___
Python tracker
<https://bugs.python.org/issue34226>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Fred L. Drake, Jr. :
--
versions: +Python 3.7, Python 3.8, Python 3.9 -Python 3.2, Python 3.3
___
Python tracker
<https://bugs.python.org/issue14
Fred L. Drake, Jr. added the comment:
Eric nailed it; pprint was not designed as a replacement for print, and was
never intended to serve that purpose.
Rejecting as out of scope.
--
resolution: -> rejected
stage: -> resolved
status: open -&g
Fred L. Drake, Jr. added the comment:
Good catch, Vinay! Thanks.
--
___
Python tracker
<https://bugs.python.org/issue36532>
___
___
Python-bugs-list mailin
Change by Fred L. Drake, Jr. :
--
nosy: +fdrake
___
Python tracker
<https://bugs.python.org/issue36532>
___
___
Python-bugs-list mailing list
Unsubscribe:
Fred L. Drake, Jr. added the comment:
Updated target to Python 3.8, since this has aged a bit.
--
versions: +Python 3.8 -Python 3.5
___
Python tracker
<https://bugs.python.org/issue9
Change by Fred L. Drake, Jr. :
--
nosy: +fdrake
___
Python tracker
<https://bugs.python.org/issue36418>
___
___
Python-bugs-list mailing list
Unsubscribe:
Fred L. Drake, Jr. added the comment:
To clarify: I'm not suggesting that an API expansion should be considered as
part of this issue.
--
___
Python tracker
<https://bugs.python.org/issue31
Fred L. Drake, Jr. added the comment:
Unfortunately, when the implementation was migrated to use
collections.namedtuple (a benefit), the _replace method wasn't extended to
support the additional computed addresses for these types.
That would really be useful.
--
nosy: +fdrake
Change by Fred L. Drake, Jr. :
--
nosy: +fdrake
___
Python tracker
<https://bugs.python.org/issue36138>
___
___
Python-bugs-list mailing list
Unsubscribe:
Fred .Flintstone added the comment:
A programmer want to instruct the computer to do something, without having to
care about how it works.
Maybe the library could in the background convert the list to a tuple.
Like:
"foo".startswith(tuple(["food", "for",
New submission from Fred .Flintstone :
The "".startswith() method accepts a string or a tuple as a parameter.
Consider adding support for list as parameter.
Example:
"foo".startswith(["food", "for", "fast"])
--
components: Interp
Fred L. Drake, Jr. added the comment:
The 3.X docs generally don't refer to the 2.X series.
What that comment is pointing out is that leaving the field identifier out (the
number inside the {...} placeholder syntax) was not in the 3.0, but added in
3.1.
Unfortunately, I don't have a 3.0
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:
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
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 for master
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:
I'm just going to presume this issue has been around a long time, but I think
that's a pretty safe presumption.
Accepting a general sequence instead of only a list would reasonable, and I'd
support a fix that caused the code to accept a general sequence
Fred L. Drake, Jr. added the comment:
I like Éric's terminology; giving a concrete name to the concept makes it a lot
easier to grasp, and this doesn't require inventing any new component terms.
Andrés, if you'd like to tackle this, that's great! I'd be happy to for you to
bounce drafts
Change by Fred L. Drake, Jr. :
--
nosy: +fdrake
___
Python tracker
<https://bugs.python.org/issue33869>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Fred L. Drake, Jr. :
--
nosy: +pablogsal
___
Python tracker
<https://bugs.python.org/issue33832>
___
___
Python-bugs-list mailing list
Unsubscribe:
Fred L. Drake, Jr. added the comment:
Indeed, I did not. Fixed now. I hope.
--
nosy: +rhettinger
___
Python tracker
<https://bugs.python.org/issue33
Fred L. Drake, Jr. added the comment:
A quick grep on the 3.7 branch indicates that the standard documentation
includes each of the terms "magic method" and "special method" about the same
number of times. (I didn't check for instances that wrapped lines.)
Perhaps we s
Fred L. Drake, Jr. added the comment:
> I saw what looked to me like a bug that's been in the code for 18 years,
> and I saw that it was a simple fix.
And you're right: It is a bug, the fix is simple, and the risk is low.
Ten years ago, I'd have probably just landed the fix
Fred L. Drake, Jr. added the comment:
New changeset 5bfa058e65897567889354d7eb34af2b93a20f18 by Fred Drake
(arikrupnik) in branch 'master':
bpo-33274: Compliance with DOM L1: return removed attribute (#7465)
https://github.com/python/cpython/commit/5bfa058e65897567889354d7eb34af2b93a20f18
Fred L. Drake, Jr. added the comment:
I should stop relying on wetware memory; it's not working out. Sorry for the
mis-information.
--
___
Python tracker
<https://bugs.python.org/issue33
Fred L. Drake, Jr. added the comment:
Python 2.7 is in security-fix-only mode, and this doesn't fit that. While I
wouldn't object to a note in the documentation, see my comments in my patch
review (there's just no place for it to go
Fred L. Drake, Jr. <fdr...@gmail.com> added the comment:
While I've no strong objection to updating to follow the specification, I also
don't see any real value here. The current minidom implementation has been
considered sufficient for many years now (if you consider the DOM des
Change by Fred L. Drake, Jr. <fdr...@gmail.com>:
--
nosy: +fdrake
___
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue1644818>
___
_
Change by Fred L. Drake, Jr. <fdr...@gmail.com>:
--
nosy: +fdrake
___
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue32706>
___
_
Fred L. Drake, Jr. <fdr...@gmail.com> added the comment:
This has landed on master and will be part of Python 3.7.
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker <rep...@bugs.
Fred L. Drake, Jr. <fdr...@gmail.com> added the comment:
New changeset 96a5e50a5de3683b2afd6d680c7ecc4b525986f6 by Fred Drake (Giuseppe
Scrivano) in branch 'master':
bpo-32143: add f_fsid to os.statvfs() (#4571)
https://github.com/python/cpython/commit/96a5e50a5de3683b2afd6d680c7ecc4b52
Fred L. Drake, Jr. <fdr...@gmail.com> added the comment:
I think Giuseppe's patch is good, but there's a Windows failure on AppVeyor, so
I'm a little wary. It doesn't look related, but I haven't looked at Python on
Windows since... 2001,
Change by Fred L. Drake, Jr. <fdr...@gmail.com>:
--
nosy: +fdrake
___
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue32143>
___
_
Change by Fred L. Drake, Jr. <fdr...@gmail.com>:
--
nosy: +fdrake
___
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue31803>
___
_
Fred L. Drake, Jr. <fdr...@gmail.com> added the comment:
The 3.5 docs should really remain in the main docs UI via the pulldown as long
as it's so widely used. The fact that it won't be changing much just means it
can be served efficiently.
--
nosy: +
Change by Fred L. Drake, Jr. <fdr...@gmail.com>:
--
nosy: +fdrake
___
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue29400>
___
_
snippets:
- http://pythontutor.com
At the "Edit code" link, you can type/paste your own Python
statements and have the tool single-step though them. At each
step, it draws the data structures with values, links to other data
structures, etc. A great Python visualization tool!
Enj
Fred L. Drake, Jr. added the comment:
On Thu, Jul 27, 2017 at 3:01 PM, Fred L. Drake, Jr.
<rep...@bugs.python.org> wrote:
> If the link went to an edit form with the version of the content the
> user was reading,
> and includes an explanation of the multiple-versions issue, i
Fred L. Drake, Jr. added the comment:
On Thu, Jul 27, 2017 at 1:03 PM, Mariatta Wijaya <rep...@bugs.python.org> wrote:
> I don't think we should add this link.
>
> When we make edits to the docs, even simple typo fixes, it should first be
> done
> in the m
Lawrence_D?Oliveiro <lawrenced...@gmail.com> wrote:
>On Thursday, June 8, 2017 at 3:41:35 PM UTC+12, Fred Fishbin wrote:
>> Yup, that seems to be the deal, and there doesn't seem tpo be a really
>>simple
>> way to deal with this.
>
>The preferred way to do file
Lawrence_D?Oliveiro <lawrenced...@gmail.com> wrote:
>On Thursday, June 8, 2017 at 3:41:35 PM UTC+12, Fred Fishbin wrote:
>> Yup, that seems to be the deal, and there doesn't seem tpo be a really
>>simple
>> way to deal with this.
>
>The preferred way to do file
anymore.
Freddie
wxjmfa...@gmail.com wrote:
Le mardi 6 juin 2017 21:37:24 UTC+2, Fred Fishbin a écrit :
>> Hi
>>
>> I want to write little program that my friend can run - he'll plug a USB
>>drive
>> into his Windows 7 PC, plug his phone in a USB port on same PC, the
-perl.html
Hope this helps,
--Fred
--
Fred Stluka -- [3]mailto:f...@bristle.com -- [4]http://bristle.com/~fred/
Bristle Software, Inc -- [5]http://bristle.com -- Glad to be of service!
Open Source: Without walls
Yup, that seems to be the deal, and there doesn't seem tpo be a really simple
way to deal with this. ...but at least I know what I need to look for.
thanks! Freddie
eryk sun <eryk...@gmail.com> wrote:
>On Tue, Jun 6, 2017 at 7:36 PM, Fred Fishbin <fredfish...@hotmail.com> wrot
Hi
I want to write little program that my friend can run - he'll plug a USB drive
into his Windows 7 PC, plug his phone in a USB port on same PC, then run my
program and it'll xfer some audiobook files over for him.
I plugged the USB drive in and it became "G:\", but the phone plugged in and
Ben,
Excellent answer! Thanks!
--Fred
Fred Stluka -- mailto:f...@bristle.com -- http://bristle.com/~fred/
Bristle Software, Inc -- http://bristle.com -- Glad to be of service!
Open Source: Without walls and fences, we
d see the M-x prompt, then then type "set-selective-display"
using tab to autocomplete it. But I can't then type a column
number after a space or in parens or anything. What am I missing?
Thanks,
--Fred
----
Fred Stluka -- m
Fred L. Drake, Jr. added the comment:
I agree that writexml should be available for document fragments.
I doubt the additional level of indentation should be added, as you've included
in point 2.
--
nosy: +fdrake
___
Python tracker <
Fred L. Drake, Jr. added the comment:
I wouldn't go so far as to say it's never come up; it's something I've thought
about a number of times, and I've waffled on it a few times.
It's not fundamentally unreasonable to want it to adapt to the current terminal
window, though I think it would
Fred L. Drake, Jr. added the comment:
This is not a problem for doctests, since the output stream is not a terminal;
the check for terminal-ness seems reasonable. (Though I don't have any idea if
it works on Windows, but it seems properly factored
Changes by Fred L. Drake, Jr. <fdr...@gmail.com>:
--
nosy: +fdrake
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue29997>
___
_
Changes by Fred L. Drake, Jr. <fdr...@gmail.com>:
--
nosy: +fdrake
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue27879>
___
_
1 - 100 of 542 matches
Mail list logo