Re: Division-Bug in decimal and mpmath

On Sat, 14 Dec 2024 at 19:02, Mark Bourne via Python-list wrote: > > Martin Ruppert wrote: > > Hi, > > > > the division 0.4/7 provides a wrong result. It should give a periodic > > decimal fraction with at most six digits, but it doesn't. > > > > Below is the comparison of the result of decimal, m

Re: Division-Bug in decimal and mpmath

2qdxy4rzwzuui...@potatochowder.com wrote: On 2024-12-14 at 12:08:29 +, Mark Bourne via Python-list wrote: Martin Ruppert wrote: Hi, the division 0.4/7 provides a wrong result. It should give a periodic decimal fraction with at most six digits, but it doesn't. Below is the comparison of

Re: Division-Bug in decimal and mpmath

On 2024-12-14 at 12:08:29 +, Mark Bourne via Python-list wrote: > Martin Ruppert wrote: > > Hi, > > > > the division 0.4/7 provides a wrong result. It should give a periodic > > decimal fraction with at most six digits, but it doesn't. > > > > Below is the comparison of the result of decima

Division-Bug in decimal and mpmath

Hi, the division 0.4/7 provides a wrong result. It should give a periodic decimal fraction with at most six digits, but it doesn't. Below is the comparison of the result of decimal, mpmath, dc and calc. 0.0571428571428571460292086417861615440675190516880580357142857 decimal: 0.4/7 0.057142857142

Re: Division-Bug in decimal and mpmath

Martin Ruppert wrote: Hi, the division 0.4/7 provides a wrong result. It should give a periodic decimal fraction with at most six digits, but it doesn't. Below is the comparison of the result of decimal, mpmath, dc and calc. 0.0571428571428571460292086417861615440675190516880580357142857 decim

Re: Bug in 3.12.5

Martin Nilsson writes: > The attached program doesn’t work in 3.12.5, but in 3.9 it worked. Attachments don't show up either on the mailing list or the newsgroup. Try again with the program inline in your post (if it's not too long). -- Keith Thompson (The_Other_Keith) keith.s.thompso...@gmail

Re: Bug in 3.12.5

On 20Sep2024 12:52, Martin Nilsson wrote: The attached program doesn’t work in 3.12.5, but in 3.9 it worked. This mailing list discards attachments. Please include your code inline in the message text. Thanks, Cameron Simpson -- https://mail.python.org/mailman/listinfo/python-list

Bug in 3.12.5

Dear Sirs ! The attached program doesn’t work in 3.12.5, but in 3.9 it worked. Best Regards Martin Nilsson -- https://mail.python.org/mailman/listinfo/python-list

Re: from __future__ import annotations bug?

> but does this mean that even with PEP 649 that forward references will > still be needed? Yes. Both of PEP 563 and PEP 649 solves not all forward reference issues. -- Inada Naoki -- https://mail.python.org/mailman/listinfo/python-list

Re: from __future__ import annotations bug?

Should mention this also affects Protocol[Buzz] On Fri, Jun 30, 2023, 5:35 PM Joseph Garvin wrote: > ``` > from __future__ import annotations > from typing import Generic, TypeVar > > T = TypeVar("T") > class Foo(Generic[T]): ... > class Bar(Foo[Buzz]): ... # NameError here > class Buzz: ... > `

from __future__ import annotations bug?

``` from __future__ import annotations from typing import Generic, TypeVar T = TypeVar("T") class Foo(Generic[T]): ... class Bar(Foo[Buzz]): ... # NameError here class Buzz: ... ``` This will error, despite the __future__ import, because cpython is trying to look up Buzz before it's defined, even

Re: Bug in io.TextIOWrapper?

On 2023-06-19, Inada Naoki wrote: > I checked TextIOWrapper source code and confirmed that it doesn't call > encoder.write(text, finish=True) on close. > Since TextIOWrapper allows random access, it is difficult to call it > automatically. So please think it as just limitatio

Re: Bug in io.TextIOWrapper?

I checked TextIOWrapper source code and confirmed that it doesn't call encoder.write(text, finish=True) on close. Since TextIOWrapper allows random access, it is difficult to call it automatically. So please think it as just limitation rather than bug. Please use codec and binary file manuall

Re: Bug in io.TextIOWrapper?

You can use file instead of BytesIO 2023年6月20日(火) 3:05 Peter J. Holzer via Python-list : > On 2023-06-20 02:15:00 +0900, Inada Naoki via Python-list wrote: > > stream.flush() doesn't mean final output. > > Try stream.close() > > After close() the value isn't available any more: > > Python 3.11.2

Re: Bug in io.TextIOWrapper?

On 2023-06-20 02:15:00 +0900, Inada Naoki via Python-list wrote: > stream.flush() doesn't mean final output. > Try stream.close() After close() the value isn't available any more: Python 3.11.2 (main, Mar 13 2023, 12:18:29) [GCC 12.2.0] on linux Type "help", "copyright", "credits" or "license" fo

Re: Bug in io.TextIOWrapper?

gistry, and then it uses the IncrementalEncoder and > IncrementalDecoder classes for the appropriate codec. > > The IncrementalEncoder.encode() function is given the object to encode > of course, and also an optional second parameter which indicates if > this is the final output. &g

Bug in io.TextIOWrapper?

der.encode() function is given the object to encode of course, and also an optional second parameter which indicates if this is the final output. The bug is that TextIOWrapper() never sets the second parameter to indicate that the output is complete - not even if you call close(). Example: >

Re: Bug 3.11.x behavioral, open file buffers not flushed til file closed.

aapost wrote at 2023-3-5 09:35 -0500: > ... >If a file is still open, even if all the operations on the file have >ceased for a time, the tail of the written operation data does not get >flushed to the file until close is issued and the file closes cleanly. This is normal: the buffer is flushed if

Re: Bug 3.11.x behavioral, open file buffers not flushed til file closed.

On 3/5/23 19:02, Cameron Simpson wrote: On 05Mar2023 10:38, aapost wrote: Additionally (not sure if this still applies): flush() does not necessarily write the file’s data to disk. Use flush() followed by os.fsync() to ensure this behavior. Yes. You almost _never_ need or want this behaviour

Re: Bug 3.11.x behavioral, open file buffers not flushed til file closed.

On 3/5/23 09:35, aapost wrote: I have run in to this a few times and finally reproduced it. Whether it is as expected I am not sure since it is slightly on the user, but I can think of scenarios where this would be undesirable behavior.. This occurs on 3.11.1 and 3.11.2 using debian 12 testing,

Re: Bug 3.11.x behavioral, open file buffers not flushed til file closed.

000): print(i,file=f) From: Python-list on behalf of aapost Date: Sunday, March 5, 2023 at 6:33 PM To: python-list@python.org Subject: Bug 3.11.x behavioral, open file buffers not flushed til file closed. *** Attention: This is an external email. Use caution responding, opening attachments or c

Re: Bug 3.11.x behavioral, open file buffers not flushed til file closed.

> On 6 Mar 2023, at 01:42, Greg Ewing via Python-list > wrote: > > On 6/03/23 1:02 pm, Cameron Simpson wrote: >> Also, fsync() need not expedite the data getting to disc. It is equally >> valid that it just blocks your programme _until_ the data have gone to disc. > > Or until it *thinks* t

Re: Bug 3.11.x behavioral, open file buffers not flushed til file closed.

On Mon, 6 Mar 2023 at 12:41, Greg Ewing via Python-list wrote: > > On 6/03/23 1:02 pm, Cameron Simpson wrote: > > Also, fsync() need not expedite the data getting to disc. It is equally > > valid that it just blocks your programme _until_ the data have gone to > > disc. > > Or until it *thinks* th

Re: Bug 3.11.x behavioral, open file buffers not flushed til file closed.

On 6/03/23 1:02 pm, Cameron Simpson wrote: Also, fsync() need not expedite the data getting to disc. It is equally valid that it just blocks your programme _until_ the data have gone to disc. Or until it *thinks* the data has gone to the disk. Some drives do buffering of their own, which may i

Re: Bug 3.11.x behavioral, open file buffers not flushed til file closed.

On 05Mar2023 10:38, aapost wrote: Additionally (not sure if this still applies): flush() does not necessarily write the file’s data to disk. Use flush() followed by os.fsync() to ensure this behavior. Yes. You almost _never_ need or want this behaviour. A database tends to fsync at the end o

Re: Bug 3.11.x behavioral, open file buffers not flushed til file closed.

On 3/5/23, aapost wrote: > > If a file is still open, even if all the operations on the file have > ceased for a time, the tail of the written operation data does not get > flushed to the file until close is issued and the file closes cleanly. This is normal behavior for buffered file I/O. There'

Re: Bug 3.11.x behavioral, open file buffers not flushed til file closed.

On 05Mar2023 09:35, aapost wrote: I have run in to this a few times and finally reproduced it. Whether it is as expected I am not sure since it is slightly on the user, but I can think of scenarios where this would be undesirable behavior.. This occurs on 3.11.1 and 3.11.2 using debian 12 test

Re: Bug 3.11.x behavioral, open file buffers not flushed til file closed.

Am 05.03.23 um 15:35 schrieb aapost: I have run in to this a few times and finally reproduced it. Whether it is as expected I am not sure since it is slightly on the user, but I can think of scenarios where this would be undesirable behavior.. This occurs on 3.11.1 and 3.11.2 using debian 12 te

Re: Bug 3.11.x behavioral, open file buffers not flushed til file closed.

On 3/5/23 09:35, aapost wrote: Guess it could just be an annoying gotcha thing on me. calling at least f.flush() in any cases where an explicit close is delayed would be the solution. Additionally (not sure if this still applies): flush() does not necessarily write the file’s data to disk.

Bug 3.11.x behavioral, open file buffers not flushed til file closed.

I have run in to this a few times and finally reproduced it. Whether it is as expected I am not sure since it is slightly on the user, but I can think of scenarios where this would be undesirable behavior.. This occurs on 3.11.1 and 3.11.2 using debian 12 testing, in case the reasoning lingers

Re: Regular Expression bug?

On Thu, Mar 2, 2023 at 9:56 PM Alan Bawden wrote: > > jose isaias cabrera writes: > >On Thu, Mar 2, 2023 at 2:38 PM Mats Wichmann wrote: > >This re is a bit different than the one I am used. So, I am trying to match >everything after 'pn=': > >import re >s = "pm=jose pn=2017"

Re: Regular Expression bug?

rera > Sent: Thursday, March 2, 2023 8:07 PM > To: Mats Wichmann > Cc: python-list@python.org > Subject: Re: Regular Expression bug? > > On Thu, Mar 2, 2023 at 2:38 PM Mats Wichmann wrote: > > > > On 3/2/23 12:28, Chris Angelico wrote: > > > On Fri, 3 Mar

Re: Regular Expression bug?

On Thu, Mar 2, 2023 at 8:30 PM Cameron Simpson wrote: > > On 02Mar2023 20:06, jose isaias cabrera wrote: > >This re is a bit different than the one I am used. So, I am trying to > >match > >everything after 'pn=': > > > >import re > >s = "pm=jose pn=2017" > >m0 = r"pn=(.+)" > >r0 = re.compile(m0)

Re: Regular Expression bug?

jose isaias cabrera writes: On Thu, Mar 2, 2023 at 2:38 PM Mats Wichmann wrote: This re is a bit different than the one I am used. So, I am trying to match everything after 'pn=': import re s = "pm=jose pn=2017" m0 = r"pn=(.+)" r0 = re.compile(m0) s0 = r0.match(s) >>

Re: Regular Expression bug?

On 02Mar2023 20:06, jose isaias cabrera wrote: This re is a bit different than the one I am used. So, I am trying to match everything after 'pn=': import re s = "pm=jose pn=2017" m0 = r"pn=(.+)" r0 = re.compile(m0) s0 = r0.match(s) `match()` matches at the start of the string. You want r0.se

RE: Regular Expression bug?

;> s0 -Original Message- From: Python-list On Behalf Of jose isaias cabrera Sent: Thursday, March 2, 2023 8:07 PM To: Mats Wichmann Cc: python-list@python.org Subject: Re: Regular Expression bug? On Thu, Mar 2, 2023 at 2:38 PM Mats Wichmann wrote: > > On 3/2/23 12:28

Re: Regular Expression bug?

t; >> > >> import re > >> s = "pn=align upgrade sd=2023-02-" > >> ro = re.compile(r"pn=(.+) ") > >> r0=ro.match(s) > >>>>> print(r0.group(1)) > >> align upgrade > >> > >> > >> This is

RE: Regular Expression bug?

On Behalf Of jose isaias cabrera Sent: Thursday, March 2, 2023 2:23 PM To: python-list@python.org Subject: Regular Expression bug? Greetings. For the RegExp Gurus, consider the following python3 code: import re s = "pn=align upgrade sd=2023-02-" ro = re.compile(r"pn=(.+) &

Re: Regular Expression bug?

n upgrade sd=2023-02-" > > ro = re.compile(r"pn=(.+) ") > > r0=ro.match(s) > > >>> print(r0.group(1)) > > align upgrade > > > > > > This is wrong. It should be 'align' because the group only goes up-to > > the space. Thought

Re: Regular Expression bug?

p(1)) align upgrade This is wrong. It should be 'align' because the group only goes up-to the space. Thoughts? Thanks. Not a bug. Find the longest possible match that fits this; as long as you can find a space immediately after it, everything in between goes into the .+ part. If you

Re: Regular Expression bug?

) > align upgrade > > > This is wrong. It should be 'align' because the group only goes up-to > the space. Thoughts? Thanks. The bug is in your regular expression; the plus modifier is greedy. If you want to match up to the first space, then you'll need somethin

Re: Regular Expression bug?

gt; print(r0.group(1)) > align upgrade > > > This is wrong. It should be 'align' because the group only goes up-to > the space. Thoughts? Thanks. > Not a bug. Find the longest possible match that fits this; as long as you can find a space immediately after it, everythin

Regular Expression bug?

Greetings. For the RegExp Gurus, consider the following python3 code: import re s = "pn=align upgrade sd=2023-02-" ro = re.compile(r"pn=(.+) ") r0=ro.match(s) >>> print(r0.group(1)) align upgrade This is wrong. It should be 'align' because the group only goes up-to the space. Thoughts? Thanks.

Re: Possible re bug when using ".*"

On 2022-12-28 19:07:06 +, MRAB wrote: > On 2022-12-28 18:42, Alexander Richert - NOAA Affiliate via Python-list > wrote: > > print(re.sub(".*", "replacement", "pattern")) > > yields the output "replacementreplacement". [...] > It&

Re: Possible re bug

Please please fix you email client so that your replies stay with the emails you are replying to. Barry On 28/12/2022 19:09, Stefan Ram wrote: Alexander Richert writes: |print(re.findall(".*","pattern")) |yields ['pattern',''] which is not what I was expecting. The asterisk is "greedy", so

Re: Possible re bug when using ".*"

output "replacementreplacement". This behavior does not occur in 3.6. Which behavior is the desired one? Perhaps relatedly, I noticed that even in 3.6, the code print(re.findall(".*","pattern")) yields ['pattern',''] which is not what I was expecti

Re: Possible re bug when using ".*"

ent". This behavior does not occur in 3.6. Which behavior is the desired one? Perhaps relatedly, I noticed that even in 3.6, the code print(re.findall(".*","pattern")) yields ['pattern',''] which is not what I was expecting. It's not a bug, it&#x

Re: Possible re bug when using ".*"

Roel Schroeven schreef op 28/12/2022 om 19:59: Alexander Richert - NOAA Affiliate via Python-list schreef op 28/12/2022 om 19:42: In a couple recent versions of Python (including 3.8 and 3.10), the following code: import re print(re.sub(".*", "replacement", "pattern")) yields the output "repla

Re: Possible re bug when using ".*"

Alexander Richert - NOAA Affiliate via Python-list schreef op 28/12/2022 om 19:42: In a couple recent versions of Python (including 3.8 and 3.10), the following code: import re print(re.sub(".*", "replacement", "pattern")) yields the output "replacementreplacement". This behavior does not occu

Possible re bug when using ".*"

In a couple recent versions of Python (including 3.8 and 3.10), the following code: import re print(re.sub(".*", "replacement", "pattern")) yields the output "replacementreplacement". This behavior does not occur in 3.6. Which behavior is the desired one? Perhaps relatedly, I noticed that even i

Bug report - Python 3.10 from Microsoft Store - IDLE won't start

Hello, IDLE won't start if ver. 3.10 is installed from Microsoft Store. 3.9 works just fine. Thanks in advance! Johan Gunnarsson Lunds universitet Medicinska fakulteten Bibliotek & IKT Box 118, 221 00 Lund Besöksadress: Sölvegatan 19, 221 84 Lund

Re: Python 3.7+ cannot print unicode characters when output is redirected to file - is this a bug?

ot;en-US", with fallback to UTF-8 if the given locale has no legacy code page. Note that setting the system to use UTF-8 also affects the host process for console sessions (i.e. conhost.exe or openconsole.exe), since it defaults to using the OEM code page (UTF-8 in this case). Unfortunately, a le

Re: Python 3.7+ cannot print unicode characters when output is redirected to file - is this a bug?

On 11/13/2022 9:49 AM, Jessica Smith wrote: Consider the following code ran in Powershell or cmd.exe: $ python -c "print('└')" └ $ python -c "print('└')" > test_file.txt Traceback (most recent call last): File "", line 1, in File "C:\Program Files\Python38\lib\encodings\cp1252.py", line

Re: Python 3.7+ cannot print unicode characters when output is redirected to file - is this a bug?

> On 13 Nov 2022, at 14:52, Jessica Smith <12jessicasmit...@gmail.com> wrote: > > Consider the following code ran in Powershell or cmd.exe: > > $ python -c "print('└')" > └ > > $ python -c "print('└')" > test_file.txt > Traceback (most recent call last): > File "", line 1, in > File "C:\Pr

Python 3.7+ cannot print unicode characters when output is redirected to file - is this a bug?

Consider the following code ran in Powershell or cmd.exe: $ python -c "print('└')" └ $ python -c "print('└')" > test_file.txt Traceback (most recent call last): File "", line 1, in File "C:\Program Files\Python38\lib\encodings\cp1252.py", line 19, in encode return codecs.charmap_encode(i

Re: Python3.6 tkinter bug?

On Wednesday, February 1, 2017 at 11:55:35 AM UTC, Terry Reedy wrote: > On 2/1/2017 1:37 AM, Christian Gollwitzer wrote: > > Am 01.02.17 um 00:02 schrieb MRAB: > >> On 2017-01-31 22:34, Christian Gollwitzer wrote: > .!frame.!checkbutton > .!frame.!checkbutton2 > .!frame2.!checkb

Re: Python3.6 tkinter bug?

On Wednesday, February 1, 2017 at 11:55:35 AM UTC, Terry Reedy wrote: > On 2/1/2017 1:37 AM, Christian Gollwitzer wrote: > > Am 01.02.17 um 00:02 schrieb MRAB: > >> On 2017-01-31 22:34, Christian Gollwitzer wrote: > .!frame.!checkbutton > .!frame.!checkbutton2 > .!frame2.!checkb

Fwd: [pandas-dev/pandas] BUG: I CANT TO RECIEVING OUTPUT FROM DATAFRAME (Issue #48256)

הודעה שהועברה -- מאת: *נתי שטרן* תאריך: יום שישי, 26 באוגוסט 2022 נושא: Re: [pandas-dev/pandas] BUG: I CANT TO RECIEVING OUTPUT FROM DATAFRAME (Issue #48256) אל: pandas-dev/pandas < reply+abnbjwpfil765hhzxpb3l4wbcubnzevbnhhfbdb...@reply.github.com> עותק: pandas-dev/

Re: Fwd: timedelta object recursion bug

Please stay on the list (such that others can help, too) Ben Hirsig wrote at 2022-7-29 06:53 +1000: >Thanks for the replies, I'm just trying to understand why this would be >useful? > >E.g. why does max need a min/max/resolution, and why would these attributes >themselves need a min/max/resolution

Re: Fwd: timedelta object recursion bug

Ben Hirsig wrote at 2022-7-28 19:54 +1000: >Hi, I noticed this when using the requests library in the response.elapsed >object (type timedelta). Tested using the standard datetime library alone >with the example displayed on >https://docs.python.org/3/library/datetime.html#examples-of-usage-timedel

Re: Fwd: timedelta object recursion bug

= timedelta(days=365) >>print(year.max) > 9 days, 23:59:59.99 >>print(year.max.min.max.resolution.max.min) > -9 days, 0:00:00 Why do you think this is a bug? -- https://mail.python.org/mailman/listinfo/python-list

Re: Fwd: timedelta object recursion bug

On 28/07/2022 10:54, Ben Hirsig wrote: Hi, I noticed this when using the requests library in the response.elapsed object (type timedelta). Tested using the standard datetime library alone with the example displayed on https://docs.python.org/3/library/datetime.html#examples-of-usage-timedelta

Fwd: timedelta object recursion bug

Hi, I noticed this when using the requests library in the response.elapsed object (type timedelta). Tested using the standard datetime library alone with the example displayed on https://docs.python.org/3/library/datetime.html#examples-of-usage-timedelta It appears as though the timedelta object

Re: bug in python 3.10.4

On Thu, 26 May 2022 19:56:16 +1200, dn declaimed the following: Commentary meant for the OP, not "dn". >Please reply to the list. Others may be able to assist (particularly if >they use MS-Windows!). > > >> Removing the quit does not help with the problem. >> >> input 10 x 10

Re: bug in python 3.10.4

On 2022-05-26 02:46, Shuaib Akhtar wrote: When double clicking a .py file when have python install. It run file but at a spot of the program it stop running. But using the built-in ide for python this problem does not happen also any other ide it work fine When you double-click on a

Re: bug in python 3.10.4

Please reply to the list. Others may be able to assist (particularly if they use MS-Windows!). > Removing the quit does not help with the problem. > > input 10 x 10 What was the result, or the exception report. Once again: did MS-Windows finish the job and close the window before you could se

Re: bug in python 3.10.4

On 26/05/2022 13.46, Shuaib Akhtar wrote: >When double clicking a .py file when have python install. It run file but >at a spot of the program it stop running. But using the built-in ide for >python this problem does not happen also any other ide it work fine Please provide (minimal) e

bug in python 3.10.4

When double clicking a .py file when have python install. It run file but at a spot of the program it stop running. But using the built-in ide for python this problem does not happen also any other ide it work fine       -- https://mail.python.org/mailman/listinfo/python-list

Re: [docs] Reporting a Bug

ot; To: d...@python.org Cc: python-list@python.org Sent: Wednesday, 4 May, 22 At 10:36 Subject: [docs] Reporting a Bug Hello dears, First of all i am not sure about this issue please advise me if there is any mistake in my report. for example in python 3.6.3 shell: x= "Th

Re: Reportlab / platypus bug?

Greg Ewing ezt írta (időpont: 2022. márc. 16., Sze, 1:01): > On 16/03/22 2:20 am, Les wrote: > > I tried to subscribe (twice), but never got the confirmation > > email. Checked in the spam folder too, but it is nowhere to be found. > > Is there any chance your email provider has some kind of quar

Re: Reportlab / platypus bug?

On 16/03/22 2:20 am, Les wrote: I tried to subscribe (twice), but never got the confirmation email. Checked in the spam folder too, but it is nowhere to be found. Is there any chance your email provider has some kind of quarantine system separate from your spam folder? The University of Canter

Re: Reportlab / platypus bug?

On 15/03/2022 13:20, Les wrote: Robin Becker ezt írta (időpont: 2022. márc. 15., K, 14:06): Hi Les, so far as I know the reportlab-users list is still running it is hosted (nad has been for many years) at https://pairlist2.pair.net/mailman/listinfo/reportlab-users is that the address you

Re: Reportlab / platypus bug?

> > > > > as a test I subscribed under my private email address and the list > responded pretty quickly; the request confirmation > email ended up in spam though. I believe the list is a fairly old version > of mailman, but I don't have any access to the > server. > I tried again, and now I got the

Re: Reportlab / platypus bug?

.. Hi Les, so far as I know the reportlab-users list is still running it is hosted (nad has been for many years) at https://pairlist2.pair.net/mailman/listinfo/reportlab-users is that the address you used? I see messages in the archives so some people can use it.-- Robin Becker as

Re: Reportlab / platypus bug?

Robin Becker ezt írta (időpont: 2022. márc. 15., K, 14:06): > > > Hi Les, so far as I know the reportlab-users list is still running it is > hosted (nad has been for many years) at > > > https://pairlist2.pair.net/mailman/listinfo/reportlab-users > > is that the address you used? I see messages i

Re: Reportlab / platypus bug?

On 14/03/2022 18:17, Les wrote: Unfortunately, the reportlab-users mailing list is unavailable (I cannot subscribe). There is paid support but since I already have a workaround, I won't pay for this. I think this is a documentation error of the reportlab package. (They do not mention that stories

Re: Reportlab / platypus bug?

Dennis Lee Bieber ezt írta (időpont: 2022. márc. 14., H 20:03): > On Mon, 14 Mar 2022 19:17:31 +0100, Les declaimed the > following: > > >Unfortunately, the reportlab-users mailing list is unavailable (I cannot > >subscribe). There is paid support but since I already have a workaround, I > >won'

Re: Reportlab / platypus bug?

On Mon, 14 Mar 2022 19:17:31 +0100, Les declaimed the following: >Unfortunately, the reportlab-users mailing list is unavailable (I cannot >subscribe). There is paid support but since I already have a workaround, I >won't pay for this. I think this is a documentation error of the reportlab >packa

Re: Reportlab / platypus bug?

ially Sensitive Business Data > > -Original Message- > From: Les > Sent: Sunday, March 13, 2022 4:56 PM > To: python-list@python.org > Subject: Reportlab / platypus bug? > > Hello, > > I have found an error, and I created a minimal working example. The > minimal working e

RE: Reportlab / platypus bug?

. Is there possibly a better place to ask this question? Teledyne Confidential; Commercially Sensitive Business Data -Original Message- From: Les Sent: Sunday, March 13, 2022 4:56 PM To: python-list@python.org Subject: Reportlab / platypus bug? Hello, I have found an error, and I

Re: Reportlab / platypus bug?

Good point. I can confirm, that it works with copy.deepcopy. Probably you are right, the story is somehow consumed by doc.build. But it is not documented anywhere. I'm going to submit a bug report, thanks. -- https://mail.python.org/mailman/listinfo/python-list

Re: Reportlab / platypus bug?

On Sun, 13 Mar 2022 21:55:36 +0100, Les declaimed the following: >It is hard to explain as it is, but something even more interesting happens >if you try to make them totally independent, and create a copy of the story >as well: > >import copy >doc = SimpleDocTemplate("phello.pdf") >doc.build(co

Re: Reportlab / platypus bug?

On 13 Mar 2022, at 22:34, Les wrote: > >  > I will, thanks. I just wanted to make sure that this is a real bug, and not a > mistake on my side. You followed the docs and got an error. Doc error? Docs out of date? Barry > > Barry ezt írta (időpont: 2022. márc. 13., V 23:29

Re: Reportlab / platypus bug?

I will, thanks. I just wanted to make sure that this is a real bug, and not a mistake on my side. Barry ezt írta (időpont: 2022. márc. 13., V 23:29): > > > > On 13 Mar 2022, at 21:41, Les wrote: > > > > I have found an error, and I created a minimal working example. T

Re: Reportlab / platypus bug?

> On 13 Mar 2022, at 21:41, Les wrote: > > I have found an error, and I created a minimal working example. The minimal > working example starts with the very first example from Platypus user guide: I would suggest that you report to reportlab.com directly, any fix will come from them. Barry

Reportlab / platypus bug?

Hello, I have found an error, and I created a minimal working example. The minimal working example starts with the very first example from Platypus user guide: from reportlab.platypus import SimpleDocTemplate, Paragraph, Spacer from reportlab.lib.styles import getSampleStyleSheet from reportlab

Is the bug reported to python Recently i upgraded my python version and its directory But when i try to download pyqt5 it gives out a holy error Do i have to install py 3.9 again pls help me take a lo

-- https://mail.python.org/mailman/listinfo/python-list

Re: Bug in email.generator.BytesGenerator() [was: Why does SMTP.send_message() do from mangling?]

On 2021-09-27, Grant Edwards wrote: > According to > https://docs.python.org/3/library/email.generator.html#email.generator.BytesGenerator > the default from mangling behavior is _supposed_ to obey the message > policy if no policy or mangle_from_ value was > provided to the call to BytesGenerato

Bug in email.generator.BytesGenerator() [was: Why does SMTP.send_message() do from mangling?]

behavior when no policy or mangle_from_ value is passed to BytesGenerator() is to enable from mangling regardless of the message's policy. I belive that is a bug. This can be worked around by changing 983 g = email.generator.BytesGenerator(bytesmsg) to 983

Re: How Do I Get A Bug In Multiprocessing Fixed?

On 6/17/2021 5:02 PM, Michael Boom wrote: The below issue is pretty serious and it is preventing me from using a system I wrote on a larger scale. How do I get this bug fixed? Thanks. https://bugs.python.org/issue43329 Reduce your code to the minimum needed to exhibit the problem. Then run

Re: How Do I Get A Bug In Multiprocessing Fixed?

On Fri, 18 Jun 2021 at 15:27, Michael Boom wrote: > The below issue is pretty serious and it is preventing me from using a > system I wrote on a larger scale. How do I get this bug fixed? Thanks. > https://bugs.python.org/issue43329 On Fri, 18 Jun 2021 at 06:07, Alexander Neils

Re: How Do I Get A Bug In Multiprocessing Fixed?

cessing\managers.py", > line 532, in connect >conn = Client(self._address, authkey=self._authkey) > File > "C:\Users\Alexander\AppData\Local\Programs\Python\Python37\lib\multiprocessing\connection.py", > line 492, in Client > c = SocketClient(addres

Re: How Do I Get A Bug In Multiprocessing Fixed?

neilson.net.nz 021 329 681 022 456 2326 On Fri, 18 Jun 2021 at 15:27, Michael Boom wrote: > The below issue is pretty serious and it is preventing me from using a > system I wrote on a larger scale. How do I get this bug fixed? Thanks. > https://bugs.python.org/issue43329 > -- > https://mail.python.org/mailman/listinfo/python-list > -- https://mail.python.org/mailman/listinfo/python-list

How Do I Get A Bug In Multiprocessing Fixed?

The below issue is pretty serious and it is preventing me from using a system I wrote on a larger scale. How do I get this bug fixed? Thanks. https://bugs.python.org/issue43329 -- https://mail.python.org/mailman/listinfo/python-list

Re: Neither pdb or print() displays the bug [FIXED]

On Tue, 1 Jun 2021, Rich Shepard wrote: I'm stuck with neither approach (pdb, print()) working. I moved the database code to a separate module, datasource.py, and when I run the activitytypes.py module (using pdb and having entered print() statements at various places in both the datasource and

Re: Neither pdb or print() displays the bug

On Sun, 6 Jun 2021, Fabio Zadrozny wrote: Hint: you should be able to use https://pypi.org/project/pytest-qt/ to unit-test a PyQt application... Fabio, Thank you for confirming this. I hadn't remembered the name so your URL is really helpful. Regards, Rich -- https://mail.python.org/mailman

Re: Neither pdb or print() displays the bug

Em qua., 2 de jun. de 2021 às 09:34, Rich Shepard escreveu: > On Wed, 2 Jun 2021, Peter Otten wrote: > > > Do you have unit tests? Those are an excellent tool to ensure that the > > components of an application work as expected and that those components > > have well-defined interfaces. Debugging

Re: Interpreter Bug

> On 2 Jun 2021, at 10:34, Alice Braim wrote: > > Good morning- > > > > I am having some very serious issues with Python, and I was hoping you > could help? > > I downloaded both Python and PyCharm, and the 2 do not seem to be working. > Every time I select Python as an interpret

Interpreter Bug

Good morning- I am having some very serious issues with Python, and I was hoping you could help? I downloaded both Python and PyCharm, and the 2 do not seem to be working. Every time I select Python as an interpreter, the whole thing crashes. Obviously, I went onto repairs, bu

Re: Neither pdb or print() displays the bug

On Wed, 2 Jun 2021, Peter Otten wrote: Do you have unit tests? Those are an excellent tool to ensure that the components of an application work as expected and that those components have well-defined interfaces. Debugging a failing unittest is usually easier than to debug a complex application.

  1   2   3   4   5   6   7   8   9   10   >