New submission from John Hagen :
multiprocessing.set_start_method() has a `force` argument that is not
documented:
https://docs.python.org/3.10/library/multiprocessing.html#multiprocessing.set_start_method
--
assignee: docs@python
components: Documentation
messages: 416451
nosy: John
John Paul Adrian Glaubitz added the comment:
> Awesome, thanks! I'll give it a try later today or tomorrow.
I have applied the patch and the problem seems to have been fixed. \o/
--
___
Python tracker
<https://bugs.python.org
John Paul Adrian Glaubitz added the comment:
Awesome, thanks! I'll give it a try later today or tomorrow.
--
___
Python tracker
<https://bugs.python.org/is
John Paul Adrian Glaubitz added the comment:
Hi Serhiy!
> The simple fix is to add UnicodeEncodeError to "except LookupError". But
> there may be other places where we can get a similar error. They should be
> fixed too.
I would be very interested to test this as t
New submission from John K. :
map(f, itr) is supposed to be the lazy way to do [f(val) for val in itr].
However, when unpacking and zipping a list of maps, I get a different result
from when evaluating eagerly. More precisely:
Python 3.10.2 | packaged by conda-forge | (main, Mar 8 2022, 15
Change by John Mellor :
--
nosy: +johnmellor
___
Python tracker
<https://bugs.python.org/issue39529>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by John :
Removed file: https://bugs.python.org/file47370/Python 3.6.4
(32-bit)_20180107153053[3191].log
___
Python tracker
<https://bugs.python.org/issue32
Change by John :
Removed file: https://bugs.python.org/file47373/Python 3.6.4
(32-bit)_20180107153053_000_core_JustForMe[3206].log
___
Python tracker
<https://bugs.python.org/issue32
New submission from John Snow :
Hi, asyncio.create_unix_server appears to treat the "backlog" parameter as
where 0 means that *no connection will ever possibly be pending*, which (at the
very least for UNIX sockets on my machine) is untrue.
Consider a (non-asyncio) server:
```pyt
John Belmonte added the comment:
PEP at https://github.com/python/peps/pull/2295
--
___
Python tracker
<https://bugs.python.org/issue45995>
___
___
Python-bug
John Belmonte added the comment:
Thank you Mark and Eric.
> I'll note that the paper is proposing a 'z' modifier to the sign, so I guess
> for us that would translate to: [sign[optional-z]] instead of just sign. I'd
> have to noodle through the differences be
John L added the comment:
It causes an exception and traceback, don't remember which exception six months
later. I'll see if I can add a suitable test case to the unit test.
--
___
Python tracker
<https://bugs.python.o
John Marshall added the comment:
Ping -- This issue has an associated PR that expands the
multiprocessing.Process.exitcode documentation to cover normal, sys.exit(), and
exception-raised termination of the child process.
https://github.com/python/cpython/pull/30142
The PR has been
John Belmonte added the comment:
Mark, would you give it a review this month? (PR has been marked stale.)
--
___
Python tracker
<https://bugs.python.org/issue45
Change by John Millikin :
--
nosy: -jmillikin
___
Python tracker
<https://bugs.python.org/issue46376>
___
___
Python-bugs-list mailing list
Unsubscribe:
John Paul Adrian Glaubitz added the comment:
I'm running into exactly this issue when using 'offlineimap' which is written
in Python.
--
nosy: +glaubitz
___
Python tracker
<https://bugs.pyt
John Holman added the comment:
Thanks - sorry to waste your time.
On Tue, 4 Jan 2022 at 18:17, Raymond Hettinger
wrote:
>
> Raymond Hettinger added the comment:
>
> The two numbers you gave become the same when rounded to the limited
> internal precision
New submission from John Holman :
Example:
str(1.12345678901234)
Out[24]: '1.123456789011'
shouldn't the last digit should be 2?
--
messages: 409696
nosy: johngholman
priority: normal
severity: normal
status: open
title: float formatting error?
type: behavior
v
Change by John Marshall :
--
keywords: +patch
pull_requests: +28360
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/30142
___
Python tracker
<https://bugs.python.org/issu
John Belmonte added the comment:
implemented float and Decimal-- PR is ready for review
--
___
Python tracker
<https://bugs.python.org/issue45995>
___
___
Pytho
John Belmonte added the comment:
potential short-term solution for Decimal:
if negative zero option is set and sign is negative:
pre-round into a temp using mpd_qrescale()
if mpd_iszero(temp):
change sign to positive
John Belmonte added the comment:
> For Decimal, we'd need to "own" the string formatting, taking that
> responsibility away from mpdecimal, but there are already other reasons to do
> that.
After some digging, I believe this is the background on forking pieces of
Change by John Belmonte :
--
keywords: +patch
nosy: +jbelmonte
nosy_count: 5.0 -> 6.0
pull_requests: +28274
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/30049
___
Python tracker
<https://bugs.python.org/i
John Belmonte added the comment:
I'll share a draft PR soon (excluding Decimal), so far it's still looking
straightforward.
> Maybe old versions would correctly ignore the new bit being set.
That's one of the benefits of using bit flags in an ABI: backward-compatible
e
John Belmonte added the comment:
I see now. PyOS_double_to_string() could gain the extra flag to coerce
negative zero but, out of the three formatting methods, only format() and
f-string would use the flag.
--
___
Python tracker
<ht
John Belmonte added the comment:
> changing %-formatting doesn't seem viable
I'm concerned about treating %-formatting specially. As far as float/complex,
the logical and efficient place to put this change seems to be
PyOS_double_to_string(), which affects all three forma
John Belmonte added the comment:
Here is the same proposal made for C++ `std::format`:
http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2020/p1496r2.pdf
It makes fair arguments for the feature's use, and explains why the problem is
hard to work around.
It was withdrawn by the a
John Belmonte added the comment:
> To normalize negative 0.0 to 0.0 you can just add 0.0.
yes, I'm aware-- see "implementation" in the original post
> there is no need to change all formatting specifications
For adding 0 to work, it must be done after the rounding. Th
New submission from John Belmonte :
proposal: add a string formatting option to normalize negative 0 values to 0
use case: rounded display of a float that is nominally 0, where the
distraction of a flashing minus sign from minute changes around 0 is unwanted
example:
>>> '%~5
New submission from John-Mark Gurney :
The documentation for Traversable.name says it is a method, not a property:
https://docs.python.org/3/library/importlib.html#importlib.abc.Traversable.name
The issue is that with Python 3.9.7 (default, Nov 1 2021, 11:26:33), using a
standard posix
New submission from John Howroyd :
>From the library documentation, it is an intended feature that an email part
>with content_maintype == "message" is treated as multipart. This does not
>seem to be compliant to MIME specification nor expected semantics. The
>attach
John Andersen added the comment:
I ran into this today. Using a wrapper function around _make_zipfile due to
https://github.com/python/cpython/blob/d5650a1738fe34f6e1db4af5f4c4edb7cae90a36/Lib/shutil.py#L817-L819
where there is a check for if the format is zip then don't pass owne
New submission from John Marshall :
<https://docs.python.org/3.11/library/multiprocessing.html#multiprocessing.Process.exitcode>
describes exitcode as
"The child’s exit code. This will be None if the process has not yet
terminated. A negative value -N indicates that the child was
Change by John Belmonte :
--
pull_requests: +27079
pull_request: https://github.com/python/cpython/pull/28731
___
Python tracker
<https://bugs.python.org/issue44
Change by John Belmonte :
--
pull_requests: +27078
pull_request: https://github.com/python/cpython/pull/28730
___
Python tracker
<https://bugs.python.org/issue44
Change by John Belmonte :
--
type: -> behavior
versions: +Python 3.10, Python 3.11, Python 3.7, Python 3.8, Python 3.9
___
Python tracker
<https://bugs.python.org/issu
New submission from John Wodder :
I use a custom script (and I'm sure many others have similar scripts as well)
for setting my prompt in Bash. It shows the name of the current venv (if any)
by querying the `VIRTUAL_ENV` environment variable, but if the venv was created
with a c
John Ehresman added the comment:
Is adding the field back an option at this point? It would mean that extensions
compiled against the release candidates may not be binary compatible with the
final release
My take is that use_tracing is an implementation and version dependent field,
and
John Snow added the comment:
Without sendmsg(), is there any other way to send SCM_RIGHTS ancillary messages
over an asyncio-managed UNIX socket?
(Is there a better place to discuss this? Kindly point me in the right
direction if so.)
--
nosy: +jnsnow
New submission from John Joseph Morelli :
I first noticed this and reported it on the W3 Schools Tutorial, the section
entitled "Add Two Numbers with User Input"
There were many behaviors that I did not understand, but for this bug report, I
will state that the input statements pr
John-Mark Gurney added the comment:
So, just looked at the patch, but it's missing the documentation part of it.
Also, yes, you can add the doc as another line, but now that's two lines (yes,
you can add semicolons to make it one line, but that might surprise some
people).
I
John-Mark Gurney added the comment:
Though this suggestion does work, I am not a fan of this solution.
The issue is that it separates the doc from the definition. This works well if
you have only a field fields in the class, But if you get 10-20+ fields, it
moves away the docs and makes it
New submission from John M. Boger :
In the documentation for sqlite3.executescript() in python 3.9+, the pseudoword
"transation" appears. I am reasonably sure "transaction" is meant, although it
could be "translation".
--
assignee: docs@python
comp
John Belmonte added the comment:
cc: ncoghlan for help with ExitStack exception context
--
nosy: +ncoghlan
___
Python tracker
<https://bugs.python.org/issue44
John Belmonte added the comment:
[reposting the example, with source]
example:
class MyException(Exception):
pass
@contextmanager
def my_cm():
try:
yield
except BaseException:
exc = MyException()
try:
raise exc
John Belmonte added the comment:
To clarify the problem case, I believe the discrepancy is seen when raising
exceptions as follows:
exc = foo()
try:
raise exc
finally:
exc.__context__ = None
(From my understanding, Trio has valid use cases for doing this since it wants
to control
John Belmonte added the comment:
demonstrating the difference for async case:
import contextlib
import trio
async def background():
assert False
async def main1():
async with trio.open_nursery() as nursery:
nursery.start_soon(background
Change by John Belmonte :
--
keywords: +patch
nosy: +jbelmonte
nosy_count: 3.0 -> 4.0
pull_requests: +25637
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/27089
___
Python tracker
<https://bugs.python.org/i
New submission from John Belmonte :
Over at the Trio project, we have evidence that
`AsyncExitStack.enter_async_context(foo())` is not actually equivalent to
`async with foo()` regarding raised exception context.
The symptom is a very long, unhelpful tracebacks because the __context__ of
John Belmonte added the comment:
> bpo-40816 took the much simpler approach of introducing a separate
> contextlib.AsyncContextDecorator class
How do I apply AsyncContextDecorator to the use case of wrapping either a sync
or async function with a synchronous context m
Change by John L :
--
keywords: +patch
pull_requests: +25299
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/26709
___
Python tracker
<https://bugs.python.org/issu
Change by John L :
--
keywords: +patch
pull_requests: +25286
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/26701
___
Python tracker
<https://bugs.python.org/issu
New submission from John L :
Some IMAP servers return an extra blank line after a counted literal value,
which makes imaplib crash.
MacOS mail and T'bird handle the blank line OK so it seems to be a somewhat
common bug.
--
components: Library (Lib)
messages: 395729
nosy: jrl
John Belmonte added the comment:
merged for Python 3.10
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
john kim added the comment:
Okay. Thank you for the detailed explanation.
--
resolution: -> not a bug
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
john kim added the comment:
Thank you for your explanation of venv.
I understand that venv is not portable.
But I was confused because the venv was written on the left side of the
terminal line and it looked like it was working.
Therefore, if venv does not work, such as if __venv_dir__ is
New submission from john kim :
I changed the path of the project using venv, so it didn't work properly.
I thought it worked successfully because there was a (venv) on the terminal
line.
However, the __VENV_DIR__ in the
set "VIRTUAL_ENV=__VENV_DIR__"
in the activate scri
New submission from John L :
In an EAI (SMTPUTF8) mail session, AUTH usernames and passwords can be UTF-8,
not just ASCII.
The fix is easy. In smtplib.py, in three places in the auth() and
auth_cram_md5() routines change ".encode('ascii')" to
".encode(self.command
John Belmonte added the comment:
> Either [...] we should lose the creation time check (not apply the
> transform), or we should still have the check (raise an error on invalid
> bits) which would still leave us in this situation.
That is only one option (which undesirable consequ
John Belmonte added the comment:
> Do you agree that simply removing the unnamed member check that takes place
> at Flag creation is a good way forward?
It's uncomfortable, because then STRICT is not actually strict, and it's going
to be show raw values in str/repr.
>
John Belmonte added the comment:
> However, if the user is interfacing with other software/hardware, they may
> not have a choice on which bits make up the mask.
I think it's the same as saying "unknown bits may come on the input". An
important use case is for forward
John Belmonte added the comment:
Rather than make such masks containing unknown bits, this would be best
practice if you want to use STRICT, correct?
NPTS_ROUND = 0x0
NPTS_CEIL = 0x1
NPTS_TRUNC = 0x2
NPTS_MASK = NPTS_ROUND | NPTS_CEIL | NPTS_TRUNC
Otherwise, if your input may have unknown
John Belmonte added the comment:
I wonder if CONFORM could tolerate these, since it's ultimately going to
discard invalid bits. And then perhaps CONFORM is the default.
--
___
Python tracker
<https://bugs.python.org/is
John Belmonte added the comment:
To clarify, it's caused by these mask entries in the enum:
NPTS_MASK = 0xF
DEL_S_MASK = 0xF0
AZIS_MASK = 0xF00
Since the masks are not an aggregation of individual bits defined in the enum,
it's an error.
> I'm inclined to go with [
John Belmonte added the comment:
I've opened a new PR, please review.
--
___
Python tracker
<https://bugs.python.org/issue42194>
___
___
Python-bugs-list m
Change by John Belmonte :
--
nosy: +jbelmonte
nosy_count: 6.0 -> 7.0
pull_requests: +24938
pull_request: https://github.com/python/cpython/pull/26348
___
Python tracker
<https://bugs.python.org/issu
John Belmonte added the comment:
A PR was opened over a year ago, but the author never signed CLA.
How can we proceed with this doc fix?
--
nosy: +John Belmonte
___
Python tracker
<https://bugs.python.org/issue42
New submission from John Nelson :
The symbol "PyStructSequence_UnnnamedField" is not *explicitly* marked for
export, causing it to be omitted from python3x.dll on Windows -- and thus
unavailable to Windows extension modules.
Attempting to use this symbol then fails at link time:
Change by John Florian :
--
nosy: -John Florian
___
Python tracker
<https://bugs.python.org/issue14243>
___
___
Python-bugs-list mailing list
Unsubscribe:
John Mish added the comment:
Thanks, I should go deeper with it before filing. Wish You have great day
Steven.
--
___
Python tracker
<https://bugs.python.org/issue43
New submission from John Mish :
A1
>>> sorted([12.001, 2, 1.999, 2.1, 4, 12])
[1.999, 2, 2.1, 4, 12, 12.002]
A2
>>> sorted([12.0001, 2, 1.999, 2.1, 4, 12])
[1.999, 2, 2.1, 4, 12.0, 12]
B1
>>> sorted([11.999, 2, 1.999,
John added the comment:
Sorry for the noise. My confusion.
--
resolution: -> not a bug
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
New submission from John :
I believe the parenthesis in
calendar.firstweekday()
should be removed. As it is, it produces 'int' cannot be called.
--
assignee: docs@python
components: Documentation
messages: 391098
nosy: JohnCC330, docs@python
priority: normal
severity: nor
Change by John Hagen :
--
keywords: +patch
pull_requests: +24133
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/25401
___
Python tracker
<https://bugs.python.org/issu
New submission from John Hagen :
The example for StringIO currently manually closes the object rather than using
a context manager. Since this is likely the first code that a new user
encounters and context managers reduce error-prone situations, I think it would
be helpful to show usage as
John Cena added the comment:
You are actually creating 4 references to the same list(See the ending *4).
This is how python behaves. See the below link as well
https://stackoverflow.com/questions/240178/list-of-lists-changes-reflected-across-sublists-unexpectedly
--
nosy
John Ehresman added the comment:
The original idea was to not use kill on win32 because developers often assume
it will work like it does on unix-like OS's -- my claim is while kill could be
improved on win32, it still won't support all the things kill can do elsewhere.
I d
John Paul Adrian Glaubitz added the comment:
I think there is one productive result of this discussion which is this patch
by Jessica Clark which gets rid of architecture-specific alignment code:
> https://github.com/python/cpython/pull/24624
Unfortunately, it has not seen any posit
John Private added the comment:
I am enclosing a PNG showing the difference between 3.9.1 and 3.9.2
In 3.9.2 the pop-up opens as a new window complete with minimise and maximise
buttons, and the position is unrelated to the turtle screen.
--
nosy: +jwmp5051
Added file: https
Dimitri John Ledkov added the comment:
BTW.
It would be advisable for Python3 to start enforcing security level 2, and
prohibit DTLS v1.1 and lower by default too. By configuring openssl library on
the host with setting security level, and/or setting min versions (if openssl
on the host
Dimitri John Ledkov added the comment:
Ubuntu 20.04+ compile OpenSSL with default security level set to 2, and further
customized security level 2 to prohibit TLS below v1.2 and DTLS below v1.2.
You can export custom openssl configuration that sets security level back to 1,
which is
New submission from John Belmonte :
time.thread_time is supposed to be available on OS X 10.12 and newer.
Yet it's reported to raise ImportError on macOS Big Sur (11.2.1) on Python
3.9.2 (python.org download). (Reported by Quentin Pradet.)
It is available in other OS X Python builds,
John Hennig added the comment:
@Floris:
> Not mentioning Path.resolve()'s behavior w.r.t. non-existing files since
that's documented in resolve() itself.
I don't see it mentioned in the documentation of `resolve()`, or anywhere else
in the docs, that on Windows (but not
John Paul Adrian Glaubitz added the comment:
Oh, and LLVM is currently gaining support M68k which you consider "legacy":
> https://reviews.llvm.org/D95315
It might be a good idea to do some research first before making su
John Paul Adrian Glaubitz added the comment:
> "Move support of legacy platforms/architectures outside Python"
> https://mail.python.org/archives/list/python-...@python.org/thread/F5BXISYP7RAINXUMYJSEYG7GCFRFAENF/
Motorola 68k isn't a 16-bit architecture, it's a 32-
John Paul Adrian Glaubitz added the comment:
> But I don't see the benefit of annoying and discouraging users who want to
> experiment with Python and with Linux on Z in 31 bit mode.
Fully agree.
> Yes, maintenance theoretically is a burden, but there have been no recent
>
John Paul Adrian Glaubitz added the comment:
> To get a platform supported by Python, we also need a volunteer to fix issues
> specific to the 31 bit s390 platform: see PEP 11.
You do not need to support every platform. Just allow your users to use them.
If something breaks downstrea
John Paul Adrian Glaubitz added the comment:
> What is the use case or benefit of building Python for 32-bit rather than
> 64-bit?
That's not really the question. The question is whether an upstream project
should prevent downstreams from using unsupported target configurations a
John Paul Adrian Glaubitz added the comment:
> Are you sure about that? It seems SLE-12 support s390x not s390. Maybe it's
> multilib support in a similar manner that I've mentioned about RHEL7?
I work at SUSE. I looked at the internal build system. Debian also still buil
John Rouillard added the comment:
Sorry for the spam, but there is no silent post setup for this tracker.
On https://github.com/python/psf-infra-meta/issues/74 in July E-paine reports
that he can't post to this issue. I just created an account linked to github to
see if I am able to
John Paul Adrian Glaubitz added the comment:
> This thread is an excellent example why ignoring platforms comes at a cost.
> It will only get worse when are going to introduce platform and architecture
> specific code for optimizations and features.
Which is purely hypothetic
John Paul Adrian Glaubitz added the comment:
> So IMO it's fine to remove the support.
You are not removing "support". You're just disallowing users to use the Python
interpreter - which works perfectly fine on all architectures we have in
current and previous relea
John Paul Adrian Glaubitz added the comment:
> The guidelines for platform support are explained in PEP 11
> (https://www.python.org/dev/peps/pep-0011/#supporting-platforms). We don't
> support platforms unless we have maintainers and CI (builtbots) in place for
> the pla
John Paul Adrian Glaubitz added the comment:
> Moving forward, s390 will be unambiguously unsupported as we cannot test
> against this platform. Unless we get a buildbot provided for this purpose,
> as well as somebody willing to fix broken builds on that buildbot long-term,
>
John Paul Adrian Glaubitz added the comment:
> I want to make it obvious that the platform has been dropped half a decade
> ago.
That's a political statement, not a technical one.
The change has zero functional impact on the other targets. It just makes the
use of Python in
John Paul Adrian Glaubitz added the comment:
s390 is a 31-bit platform, not a 32-bit platform.
I also don't see what this change achieves other than making the use of Python
3.10 on s390 harder.
It's not like the removal of support for non-threaded builds which actually
saved
John Paul Adrian Glaubitz added the comment:
> I opened this ticket after a user told me that they grepped the source code
> of Python, found the string "s390", and concluded that s390 is still
> supported by us.
Because one user was surprised by a few lines in configure
John Paul Adrian Glaubitz added the comment:
That's an argument I have personally never heard before and I have been dealing
with a lot of architecture support in many packages.
FWIW, lots of upstream projects have targets which are officially supported and
others which are there bu
John Paul Adrian Glaubitz added the comment:
And, FWIW, I generally don't quite understand what the problem with old triplet
definitions in configure.ac are. I assume they don't hurt anyone, do they?
You never know what usecases your users have and as long as a code snippe
John Paul Adrian Glaubitz added the comment:
I'm a Debian Developer and maintainer for multiple Debian Ports architectures.
Please don't remove support for Alpha, HPPA, m68k, ia64, PowerPC, SuperH, SPARC
as we're still maintaining these in Debian.
Here are the latest bu
1 - 100 of 1249 matches
Mail list logo
