David Hagen added the comment:
Should `dataclass.Field.type` become a property that evaluates the annotation
at runtime much in the same way that `get_type_hints` works?
--
nosy: +drhagen
___
Python tracker
<https://bugs.python.org/issue39
R. David Murray added the comment:
Thanks for the PR, but I've noted an issue on the review. In any case we
should agree on what goes in the repr here in this issue before actually
implementing anything.
--
___
Python tracker
<ht
David Barnett added the comment:
We were also bitten by this behavior change in
https://github.com/google/vroom/issues/110. I'm kinda baffled by the new
behavior and assumed it had to be an accidental regression, but I guess not. If
you have any other context on the BDFL conversation
R. David Murray added the comment:
AFAIR it can only be done using the roundup command line on the server.
--
nosy: +ezio.melotti
___
Python tracker
<https://bugs.python.org/issue39
R. David Murray added the comment:
Since you parsed it as a string it is not really legitimate to serialize it as
bytes. (That will work if the input message only contains ascii, but not if it
contains unicode). You'll get the same error if you replace the garbage with
the "’&quo
David Lambert added the comment:
Sometimes I say nice things about python.
https://www.quora.com/Is-Python-fast-yet/answer/David-Lambert-86?__nsrc__=4&__snid3__=6376944631
On 10/31/19 1:14 PM, Brett Cannon wrote:
> Brett Cannon added the comment:
>
> Please note that call
David Heffernan added the comment:
I would approve of that
On Tue, 7 Jan 2020, 20:43 Steve Dower, wrote:
>
> Steve Dower added the comment:
>
> In that case, we should refactor the init method to check whether handle
> has been specified earlier, so that it's obvio
David Heffernan added the comment:
Personally I'd hang this off whether handle has been specified. It seems
pointless to set the mode if you are never going to use it.
--
___
Python tracker
<https://bugs.python.org/issue39
R. David Murray added the comment:
Are you saying there is no (http) RFC compliant way to fix this, or no way to
fix it with the email library parsers? If the latter, the library is pretty
flexible and for internal stdlib use it would probably be permissible to
directly call methods
R. David Murray added the comment:
Thanks for the ping. Whether or not Serhiy's patch fixed the original problem,
the algorithm rewrite has happened so this issue is no longer relevant in any
case.
--
stage: test needed -> resolved
status: open ->
New submission from David Heffernan :
When creating an instance of CDLL (or indeed WinDLL) for a DLL that is already
loaded, you pass the HMODULE in the handle argument to the constructor.
In older versions of ctypes you could pass None as the name argument when doing
so. However
David Bolen added the comment:
Ok, I can confirm that the updated PR 17774 test passes under Windows (and
still cleans up after itself).
--
___
Python tracker
<https://bugs.python.org/issue27
David Bolen added the comment:
I'd be happy to test an updated PR 17774 on a Windows builder, but I don't
actually see any change yet. It still appears to hold the earlier
NamedTemporaryFile with mode='w' change from a few days ago
David Bolen added the comment:
The issue appears to be the temporary flag (O_TEMPORARY) that is used under
Windows with delete on close temporary files. That appears to prevent any
separate access to the file by anyone else including obtaining another
reference in the same process
New submission from David Turner :
Trying to set up shortcut function to clear screen but its not working as
expected on my Mac OS Catalina -- below is txt from idle
import os
>>> cls= lambda: os.system('clear')
>>> cls()
256
--
messages: 358908
nosy: twiste...@
R. David Murray added the comment:
I don't see the change to the test in the PR. Did you miss a push or is github
doing something wonky with the review? (I haven't used github review in a
while and I had forgetten how hard it is to use
R. David Murray added the comment:
Ideally this should be exposed by extending the content manager. Instantiating
MIME classes is part of the old API, not the new. The code in the PR may well
be correct, but class should be hidden from the normal user (of the new API).
I'm not sure what
R. David Murray added the comment:
One more tweak to the test and we'll be good to go.
--
___
Python tracker
<https://bugs.python.org/issue39040>
___
___
Pytho
R. David Murray added the comment:
Hmm. Yes, \r\n should be disallowed in the arguments to Address. I thought it
already was, so that's a bug. That bug produces the other apparent bug as
well: because the X: was treated as a separate line, the previous header did
not need double quotes
R. David Murray added the comment:
All of which isn't to discount that you might have a found a bug, by the way,
if you want to investigate further :)
--
___
Python tracker
<https://bugs.python.org/issue39
R. David Murray added the comment:
The problem is that you are starting with different inputs. unicode strings
and bytes are different things, and so parsing them can produce different
results. The fact of that matter is that email messages are defined to be
bytes, so parsing a unicode
R. David Murray added the comment:
In general your solution looks good, just a few naming comments and an
additional test request.
--
___
Python tracker
<https://bugs.python.org/issue39
R. David Murray added the comment:
The example you want to look at is get_unstructured. That shows both lookback
and modification of the parse tree to handle the whitespace between encoded
words.
--
___
Python tracker
<https://bugs.python.
R. David Murray added the comment:
And you are right that this is a very common bug in email programs. So common
that I suspect the RFC folks will eventually have to accept it as a de-facto
standard. So we do need to support it in the python email library
R. David Murray added the comment:
Yes, google should fix their bug. However, the python email package tries very
hard to interpret even RFC-non-compliant emails when there is a way to do so.
As I said, the package already tries to interpret headers such as google is
generating, it's just
R. David Murray added the comment:
That header is *completely* non-RFC compliant. If gmail generated that header
there is something very wrong in google-land :(
The RFC compliant formatting for that header looks like this:
Content-Disposition: attachment;
filename*=utf-8''Schulbesuchsbest
R. David Murray added the comment:
Thanks for the report. Can you provide an example that reproduces the problem?
Per the RFC, lines may be broken before whitespace in certain places in certain
headers, but that does not make the whitespace go away. Only the crlf sequence
is removed
Change by David Carlier :
--
keywords: +patch
pull_requests: +16932
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/17451
___
Python tracker
<https://bugs.python.org/issu
Change by David Carlier :
--
components: FreeBSD
nosy: David Carlier, koobs
priority: normal
severity: normal
status: open
title: DTrace FreeBSD build fix
versions: Python 3.9
___
Python tracker
<https://bugs.python.org/issue38
David Bolen added the comment:
I think fixing the underlying pty issue should certainly be the goal, but the
question is whether the process group change should remain active in the
meantime, as its presence is causing a regression in the tests. I think such
cases in the past are usually
R. David Murray added the comment:
The docs currently say "The returned object is a file-like object whose _file
attribute is either an io.BytesIO or io.StringIO object (depending on whether
binary or text mode was specified) or a true file object, depending on whether
rollover() has
R. David Murray added the comment:
Actually, the success path there should also check that value is empty, and if
it is not register a defect for that as well.
--
___
Python tracker
<https://bugs.python.org/issue38
R. David Murray added the comment:
I haven't looked at this in detail, but here are my general thoughts: I think
it would be reasonable to expect that the module would function even if the
file permissions are screwed up, similar to how unix commands that try to read
.netrc will (try
R. David Murray added the comment:
More tests are always good :)
The "correct" solution here (as far as I remember, its has been a while since
I've had time to even looked at the _header_value_parser code) would be to add
a new 'invalid-msg-id' token, and do this:
New submission from David Coles :
See the `recv_fds` example for `socket.recvmsg`.
This code produces a `DeprecationWarning` on current versions of Python.
https://docs.python.org/3.9/library/socket.html#socket.socket.recvmsg
--
assignee: docs@python
components: Distutils
David Cuthbert added the comment:
On the completely deprecate reuse_address and rewrite/force folks to use
reuse_port proposals, I'm a bit dubious of this approach.
Right now, we have two knobs that directly correspond to (potential)
kernel-level socket parameters, SO_REUSEADDR
David Cuthbert added the comment:
Jukka -- Fair enough; will reword this a bit. I'm trying to keep the
DeprecationWarning short enough so people's eyes don't glaze over; will see
what wordsmithing I can do here. (Once you get beyond a certain length, the
number of folks who actually read
David Cuthbert added the comment:
Alright -- my first stab at the DeprecationWarning in 3.6.
https://github.com/dacut/cpython/commit/6a1e261678975e2c70ec6b5e98e8affa28702312
Please critique away, and don't fret about bruising my ego. :-)
Is there a more idiomatic way of getting a warning
David Cuthbert added the comment:
FreeBSD 12.1 and MacOS 10.15.1 (Catalina) appear to have saner and safer
behavior.
Both require the use of SO_REUSEPORT for this behavior to happen as well.
FreeBSD also requires the UID to be the same or 0 for subsequent processes to
make the bind() call
David Cuthbert added the comment:
I'm working on patches for the deprecation bits (targeting 3.6 for now; will
work my way up from there) for review, including documentation. Unless someone
tells me to stop. :-)
In an attempt to make this not-so-Linux-specific, I'm reviewing how this works
David Cuthbert added the comment:
How much harm would there be in bringing the DeprecationWarning into the next
patch of existing (3.6, 3.7, 3.8) releases? The security implications are
significant enough that I'd want to be notified of it in my software ASAP.
Users can (and should
David K. Hess added the comment:
The documentation you quoted does read to me as compatible? The database it is
referring to is the one hardcoded in the module – not the one assembled from
that and the host OS. But, maybe this is just the vagaries of language and
perspective at play.
Anyway
David K. Hess added the comment:
Hi, I'm the author of the commit that's been fingered. Some comments about the
behavior being reported
First, as pointed out by @xtreak, indeed the mimetypes module uses mimetypes
files present on the platform to add to the built in list of mimetypes
David Nicolson added the comment:
It looks like it's just inconsistency in plutil that is causing the confusion.
/usr/libexec/PlistBuddy -c Print test.plist
Dict {
FloatExample2 = 0.10
FloatExample3 = 100.00
FloatExample = 0.00
}
cat test.plist | plutil -convert xml1
New submission from David Nicolson :
Converting float values stored as strings with the real data type can result in
an integer value or a rounding error.
import plistlib
xml = """
http://www.apple.com/DTDs/PropertyList-1.0.dtd;>
FloatExample
100.0
FloatExam
New submission from David Heffernan :
Starting with Python 3.8 certain ctypes callbacks fail to restore the stack
pointer.
In the repo below, when the DLL is compiled with MSVC under default debug
settings, running the Python script leads to a debug error dialog which says:
Run-Time Check
New submission from David Goldsmith :
When I run the second example code of Section 10.3 of The Python Tutorial:
import argparse
from getpass import getuser
parser = argparse.ArgumentParser(description='An argparse example.')
parser.add_argument('name', nargs='?', default=getuser(), help
Change by David Goldsmith :
--
title: Sug. for the scope example in TPT Cjapter 9 -> Sug. for the scope
example in TPT Chapter 9
___
Python tracker
<https://bugs.python.org/issu
New submission from David Goldsmith :
In The Python Tutorial, at the end of Section 9.2.1 "Scopes and Namespaces
Example," there occurs the statement: "You can also see that there was no
previous binding for spam before the global assignment." Indeed, one
New submission from David Lambert :
Does aksokcancel return "true" or True ? The docstring should say True This
is pervasive throughout the module. tkinter has such a mishmash of numbers
supplied as strings, strings supplied as constants making this carelessness
egregious. On
David Hagen added the comment:
This PR has been sitting for a while. Any chance we can bring it over the
finish line?
--
___
Python tracker
<https://bugs.python.org/issue34
David Steele added the comment:
I came across this thread after making a simple argparse formatter for
preserving paragraphs. The submissions here look better than that effort. Here
is a quick, hacky look at the patches from one perspective.
I wanted to prefer ParagraphFormatterML
Change by David Bolen :
--
nosy: +db3l
___
Python tracker
<https://bugs.python.org/issue38547>
___
___
Python-bugs-list mailing list
Unsubscribe:
David Bolen added the comment:
I can recreate this manually by running regrtest.py against test_pty. Crashes
with any "-j#" option, but fine when run sequentially. Removing the process
group change avoids the crash.
With the process group change in place, the trigger poi
David Bolen added the comment:
I don't know for sure that this is the cause but both 3.x builds following this
commit on my bolen-ubuntu worker (Ubuntu 18.04.3) have had test_pty crash in
the first attempt, with the retry succeeding. For example
https://buildbot.python.org/all/#/builders
Change by David Kernan :
--
pull_requests: -16262
___
Python tracker
<https://bugs.python.org/issue38413>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by David Kernan :
--
keywords: +patch
pull_requests: +16262
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/16678
___
Python tracker
<https://bugs.python.org/issu
Change by David Kernan :
--
assignee: -> docs@python
components: +Documentation -email
nosy: +docs@python
___
Python tracker
<https://bugs.python.org/issu
David Kernan added the comment:
Ah yes, thanks, this does seem pretty intentional.
I'll submit a PR for the documentation for this method for the affected version.
--
___
Python tracker
<https://bugs.python.org/issue38
Change by David Kernan :
--
title: email.utils.parsetime_tz does not return "None" ->
email.utils.parsetime_tz does not return "None" as the tz offset
___
Python tracker
<https://
Change by David Kernan :
--
type: -> behavior
___
Python tracker
<https://bugs.python.org/issue38421>
___
___
Python-bugs-list mailing list
Unsubscrib
New submission from David Kernan :
email.utils.parsetime_tz() is a function which attempts to parse a date, and
returns a 10-item tuple.
The first 9 items represents a time, and the last item represents the timezone
offset from UTC.
In Python 2, the original behavior was to return the date
David Bolen added the comment:
I've confirmed the partial read with some local modifications, and the failures
are always split between time stamp and value:
Warning -- Failed to parse typeperf output: '"10/02/2019 17:42:26.229"'
0.0
Warning -- Missing first field: ,"0.
David Bolen added the comment:
Oh, I agree it's just a warning, and I suspect few people look into warnings,
but since it's not from an actual test, I'm not sure the overall build should
be flagged.
The manual typeperf looks fine, but there's no way I could tell visually how
the I/O
David Bolen added the comment:
Just an FYI that this change is generating warnings on my Windows 10 buildbot
with some regularity about a failure to parse testperf output, such as:
Warning -- Failed to parse typeperf output: '"10/01/2019 07:58:50.056"'
from https://buildbot.pyth
Change by David CARLIER :
--
pull_requests: +16055
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/16469
___
Python tracker
<https://bugs.python.org/issu
Change by David CARLIER :
--
components: Build
nosy: devnexen
priority: normal
pull_requests: 16052
severity: normal
status: open
title: macOS sqlite 3 module build fix
type: compile error
versions: Python 3.9
___
Python tracker
<ht
David Parks added the comment:
An answer came in over the stack overflow question.
https://stackoverflow.com/questions/58019939/attributeerror-str-object-has-no-attribute-errno/58084380#58084380
The issue is that OSError implements a custom __reduce__ function which needs
to be override
David Parks added the comment:
I may be wrong here, but the issue appears to be a problem in pickle, which is
why I brought it over here. From the looks of the very simple code in the
Exception I can't see that there's any way that this exception is possible
unless pickle itself has a bug
Change by David Parks :
--
title: Pickle not deserializing an OSError exception as expected -> Pickle not
deserializing an aiohttp ClientConnectorError exception as expected
___
Python tracker
<https://bugs.python.org/issu
New submission from David Parks :
Below is a minimum reproducible test case of what appears to be an issue in
pickle.
Before pickling the exception ClientConnectionError, from aiohttp, the property
ClientConnectionError._os_error is a PermissionError object (a subclass of
OSError). After
David Parks added the comment:
Oh yes, this belongs to aiohttp. I thought that was handled here. I'll move
this to a git issue on that page, and I'm closing this.
https://github.com/aio-libs/aiohttp/issues/4077
--
resolution: -> rejected
stage: -> resolved
status: open -&g
David Parks added the comment:
Minor correction to the minimal reproducible test case:
```
import multiprocessing
import aiohttp
connection_key = aiohttp.client_reqrep.ConnectionKey
ose = OSError('test')
e = aiohttp.client_exceptions.ClientConnectorError(connection_key, ose)
q
New submission from David Parks :
Original question posted here:
https://stackoverflow.com/questions/58019939/attributeerror-str-object-has-no-attribute-errno?noredirect=1#comment102443264_58019939
The following exception is encountered when placing
Change by David Hilton :
--
keywords: +patch
pull_requests: +15877
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/16292
___
Python tracker
<https://bugs.python.org/issu
New submission from David Hilton :
If a python piece of code imports cython code with async defs,
`asyncio.iscoroutinefunction` cannot determine that the code is async.
https://github.com/cython/cython/issues/2273#issuecomment-531537624
scoder is open to marking async defs so that they can
Change by David Cuthbert :
--
versions: +Python 3.8
___
Python tracker
<https://bugs.python.org/issue34820>
___
___
Python-bugs-list mailing list
Unsubscribe:
David Cuthbert added the comment:
I'm seeing this on a rebuild now of Python 3.7.4 on Ubuntu 18.04 (in my case
against _ssl.c).
What's happening is there's coverage/profiling data being generated in the
build chain (somewhere), which spits out files named *.gcda. Interestingly,
make clean
David Bolen added the comment:
The new test_check_c_globals.ActualChecks test is failing with an "unexpected
success" on the bolen-ubuntu buildbot (under Ubuntu 18.04.3). I can reproduce
the failure in a manually built tree.
--
n
Change by David Peall :
--
nosy: +David Peall
___
Python tracker
<https://bugs.python.org/issue28747>
___
___
Python-bugs-list mailing list
Unsubscribe:
David K. added the comment:
OK,
I see your point :)
Modification of the original certificiation is legally problematic.
Much thanks for the patience and time to explain,
D.K
On Wed, Aug 14, 2019, 17:23 Christian Heimes wrote:
>
> Christian Heimes added the comment:
>
> O
David K. added the comment:
Hi,
Judging by your comment, I think there is a an unfortnate misunderstanding.
If you'd be kind enough, please let me explain:
1. The issue I had was indeed on Python 3.7, using the highly used
"requests" library. Also my change was -no
Change by David K. :
--
keywords: +patch
pull_requests: +14979
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/15260
___
Python tracker
<https://bugs.python.org/issu
New submission from David K. :
Unable to establish SSL connections using company's private certificates where
their SANs (Subject Alternative Names) contain at least one DNS Name that
starts with white spaces.
Attempting to establish SSL connection would result in Exception
David Wilson added the comment:
A real example of where returning the partial buffer is dangerous would be
EBADF.
- Repeated reading succeeds, building up a partial buffer. Another thread runs,
and buggy code causes an unrelated fd blonging to the file object to be closed.
- Original
David Wilson added the comment:
If we treat different errnos specially, the list of 'okay to silently fail'
errors seems quite succinct. In another project I treat EIO, EPIPE and
ECONNRESET as EOF, and raise all others --
https://github.com/dw/mitogen/blob
David Wilson added the comment:
Interesting, this immediately turns into a little rabbit hole :)
The reason read() is failing in this case, is because argument clinic defaults
the size parameter to -1, which redirects the call to readall(). So this issue
is actually about readall
Change by David Heiberg :
--
pull_requests: +14872
pull_request: https://github.com/python/cpython/pull/15133
___
Python tracker
<https://bugs.python.org/issue37
R. David Murray added the comment:
Right, and the python email package fully supports non ascii:
>>> msg = EmailMessage()
>>> msg['Subject'] = "Panamá- Casco Antiguo"
>>> bytes(msg)
b'Subject: =?utf-8?q?Panam=C3=A1-?= Casco Antiguo\n\n'
>>> str(msg
Change by David CARLIER :
--
components: macOS
nosy: devnexen, ned.deily, ronaldoussoren
priority: normal
pull_requests: 14815
severity: normal
status: open
title: mmap module track anonymous page on macOS
versions: Python 3.9
___
Python tracker
R. David Murray added the comment:
The input header is not valid (non-ascii is not allowed in headers), so you
shouldn't expect make_header to do anything sensible. Note that this is the
legacy API, which is a toolkit and does not hold your hand when it comes to RFC
compliance. Aside from
Change by R. David Murray :
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
New submission from David Lewis :
This issue is a follow up to previous discussions about confusing results with
asyncio.wait_for. In the current implementation, it seems unintuitive that a
coroutine with a timeout argument may easily wait forever. Perhaps wait_for
could use
Change by David Heiberg :
--
keywords: +patch
pull_requests: +14811
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/15062
___
Python tracker
<https://bugs.python.org/issu
David Heiberg added the comment:
Super, thanks for the help, I'll submit a PR as soon as it is ready
--
___
Python tracker
<https://bugs.python.org/issue37
David Heiberg added the comment:
I'm happy to take a look at this, I found one example here:
https://docs.python.org/3/library/winreg.html#winreg.DisableReflectionKey
How would I go about submitting a patch for all of the docs across the
versions? Would I apply the patch to the relevant
David Wilson added the comment:
Happy to send a patch for this if we can agree on the semantic being incorrect,
and more importantly, someone is happy to review the patch once it reaches
GitHub ;)
--
___
Python tracker
<https://bugs.python.
New submission from David Wilson :
Given:
$ cat tty-failure.py
import pty
import os
master, slave = pty.openpty()
master = os.fdopen(master, 'r+b', 0)
slave = os.fdopen(slave, 'r+b', 0)
slave.write(b'foo')
slave.close()
print(master.read())
On Python 2
David Edelsohn added the comment:
Runtime linking allows a dynamically loaded library to interpose symbols. The
classic example is allowing a program or dynamic library to overload C++
operator new. A library or program overrides the symbol by name.
Python does not require this. Python does
David Edelsohn added the comment:
Absolutely, positively no. This is horrible and completely wrong.
Applications on AIX should not be compiled to allow dynamic linking to make
them operate more like SVR4/Linux. Python does not require dynamic linking.
This simply is masking a symptom
401 - 500 of 12771 matches
Mail list logo
