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,

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 limitation rat

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 manually

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"

Re: Bug in io.TextIOWrapper?

n 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. > > The bug

Bug in io.TextIOWrapper?

() 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

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

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

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

ge(5000): 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*

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*

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

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

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.

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

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

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

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

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: 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

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 > >> > >> > >> Th

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. Thoughts? Thanks.

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 want to ex

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 something like [^ ] (i.

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, everything

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". [...] >

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",

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 expecting. It's not

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's a change in behaviour

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

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

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

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

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

n 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 legacy read from the console host does not support r

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

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

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 >

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 >

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

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

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

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

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)

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

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= "The meaning of life" x.strip("meaning") 'The meaning of lif' As you s

[issue401517] Fix for Bug 114333 (only reported bug in minidom)

Change by admin : ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue403202] fix bug parsing nested tags with htmllib

Change by admin : -- github: None -> 33698 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue483231] email.Utils.formatdate(): localtime bug

Change by admin : -- github: None -> 35546 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue212468] sre/pre bug

Change by admin : ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue213700] widespread bug in HTML files: lots of italics

Change by admin : ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue211725] Response to bug 110619

Change by admin : ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue401972] Fix for lookbehind bug (#117242)

Change by admin : ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue524008] pysvr portability bug on new POSIX hosts

Change by admin : -- github: None -> 36184 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue536578] patch for bug 462783 mmap bus error

Change by admin : -- github: None -> 36352 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue210848] Fwd: Debian Bug#40891: urllib.urlopen/urlretrieve doesn't support passive FTP (PR#58)

Change by admin : ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue527855] ftplib error (exception) handling bug

Change by admin : -- github: None -> 36232 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue210654] bug in complex_nonzero (PR#347)

Change by admin : ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue527371] Fix for sre bug 470582

Change by admin : -- github: None -> 36223 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue512799] webchecker protocol bug

Change by admin : -- github: None -> 36027 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue528990] bug? in PyImport_ImportModule under AIX

Change by admin : -- github: None -> 36245 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue532180] fix xmlrpclib float marshalling bug

Change by admin : -- github: None -> 36287 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue529408] fix random.gammavariate bug #527139

Change by admin : -- github: None -> 36253 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue529273] WeakValueDictionary.setdefault() bug

Change by admin : -- github: None -> 36252 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue526384] Bug reports are ignored

Change by admin : -- github: None -> 36211 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue487784] Fixes a bug in popen3/4 handling on UNIX

Change by admin : -- github: None -> 35645 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue478421] cPickle bug when using imp.load_source()

Change by admin : -- github: None -> 35472 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue514628] bug in pydoc on python 2.2 release

Change by admin : -- github: None -> 36047 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue468169] fix for bug #448951 (re group handling)

Change by admin : -- github: None -> 35285 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue474175] file.readinto arg parsing bug

Change by admin : -- github: None -> 35389 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue511737] ConfigParser bug/limitation

Change by admin : -- github: None -> 36013 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue492386] Cascading menu bug on Linux

Change by admin : -- github: None -> 35731 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue490330] String format bug in test_b2

Change by admin : -- github: None -> 35688 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue453059] Nasty bug in HTMLParser.py

Change by admin : -- github: None -> 35006 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue482510] bug in slicing time.struct_time

Change by admin : -- github: None -> 35535 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue422463] bug in Python 1.5.2 for win2k pro

Change by admin : -- github: None -> 34479 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue420753] Patch for bug #420725 urllib MIME header

Change by admin : -- github: None -> 34450 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue418615] regular expression bug in pipes.py.

Change by admin : -- github: None -> 34409 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue418613] regular expression bug in pipes.py

Change by admin : -- github: None -> 34408 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue405358] Python2.0 re module: greedy regexp bug

Change by admin : -- github: None -> 34046 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue403743] [windows] Correction to bug #131273

Change by admin : -- github: None -> 33904 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue430160] CGIHTTPServer.py POST bug using IE

Change by admin : -- github: None -> 34582 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue422669] Bug with appending objects to list.

Change by admin : -- github: None -> 34481 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue413850] Bug in xml/__init__.py

Change by admin : -- github: None -> 34278 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue415597] asynchat.py - bug in terminator find

Change by admin : -- github: None -> 34311 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

  1   2   3   4   5   6   7   8   9   10   >