Sean Reifschneider added the comment:
I'm attaching a new version of this which includes AMK's string patch
ported over to unicode.
Any objections to my committing this to the trunk? Should it also go in
for the next 2.5 release?
--
n
Sean Reifschneider added the comment:
This is a high priority item that hasn't been touched in half a decade.
Mark: Consider this a reminder if this is still on your agenda to do.
If not, shall we just close it? Is there anyone else that could do this?
--
nosy:
Sean Reifschneider added the comment:
I've committed some *very* basic documentation as
Doc/library/imputil.rst. This is mostly pulling the documentation I
could find in the web and in the code and setting it up in Python doc
format. I'm adding people who have recently touched the
Sean Reifschneider added the comment:
etrepum: Can you fix the test which caused this to be re-opened?
I'm tempted to push this down in priority from urgent to high, since the
code is (apparently) fixed, just the test is failing, but ideally this
could just get fixed.
--
nosy:
Changes by Sean Reifschneider:
_
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1692335>
_
___
Python-bugs-list mailing list
Unsubscribe:
http://mai
Changes by Sean Reifschneider:
_
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1692335>
_
___
Python-bugs-list mailing list
Unsubscribe:
http://mai
Sean Reifschneider added the comment:
A few comments on this one:
Perhaps the tests should be patched instead of the grp module? Because
it may be useful for someone to know that old-style NIS maps are being
referenced.
I presume if the change is made in grp that it should also be made in pwd
Changes by Sean Reifschneider:
--
assignee: -> jafo
_
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1597011>
_
___
Python-bugs-list mailing li
Sean Reifschneider added the comment:
There are some bugs in the bz2 module. The problem boils down to the
following code, notice how *c is assigned *BEFORE* the check to see if
there was a read error:
do {
BZ2_bzRead(&bzerror, f->fp, &c, 1);
f->pos++;
Sean Reifschneider added the comment:
I'm going to call this closed because this is basically a build
environment problem and the RPM can't really detect it at build time.
This is noted in the RPM building FAQ, and if you search for the
"unclear" message you will find th
Changes by Sean Reifschneider:
--
priority: -> normal
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1000>
__
___
Python-bugs-list mailing list
Uns
Sean Reifschneider added the comment:
I don't suppose you could wrangle up a proposed patch to fix this?
--
nosy: +jafo
_
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.or
Sean Reifschneider added the comment:
Is this a bug or just incorrect usage? From reading the message it
sounds like it may just have been an incorrect usage.
If it's a bug, can we get a sample that reproduces the problem?
--
nosy: +jafo
Tr
Changes by Sean Reifschneider:
--
priority: -> normal
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1001>
__
___
Python-bugs-list mailing list
Uns
Sean Reifschneider added the comment:
Removed the "works for me" resolution because I think the poster
accidentally selected this.
No patch was attached, and the referenced URL for the information is
gone now. Can the original submitter attach a patch for this. Once we
have the
Sean Reifschneider added the comment:
blaforge: I know it's been years, but can you provide code that
reproduces this? I'm going to switch it to "pending" state, please
re-open when you include some code to reproduce it.
--
sta
Sean Reifschneider added the comment:
I have committed this into trunk and the 2.5 maintenance branch. It
passes all tests and the resulting build passes the submitter-provided test.
--
status: open -> closed
_
Tracker <[EMAIL PROTECTED]&
Changes by Sean Reifschneider:
--
priority: -> low
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1020>
__
___
Python-bugs-list mailing list
Uns
Changes by Sean Reifschneider:
--
assignee: -> vsajip
nosy: +vsajip
priority: -> normal
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1021>
__
_
Changes by Sean Reifschneider:
--
priority: -> normal
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1025>
__
___
Python-bugs-list mailing list
Uns
Changes by Sean Reifschneider:
--
priority: -> high
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1042>
__
___
Python-bugs-list mailing list
Uns
Changes by Sean Reifschneider:
--
priority: -> normal
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1053>
__
___
Python-bugs-list mailing list
Uns
Changes by Sean Reifschneider:
--
assignee: -> fdrake
nosy: +fdrake
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1053>
__
___
Python-bugs-li
Changes by Sean Reifschneider:
--
priority: -> normal
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1060>
__
___
Python-bugs-list mailing list
Uns
Changes by Sean Reifschneider:
--
priority: -> normal
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1003>
__
___
Python-bugs-list mailing list
Uns
Changes by Sean Reifschneider:
--
priority: -> high
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1067>
__
___
Python-bugs-list mailing list
Uns
Sean Reifschneider added the comment:
Can you provide an example of an address that triggers this? Preferably
in a code sample that can be used to reproduce it? Uber-ideally, a
patch to the email module test suite would be great.
--
nosy: +jafo
priority: -> nor
Changes by Sean Reifschneider:
--
resolution: -> fixed
_
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1597011>
_
___
Python-bugs-li
Changes by Sean Reifschneider:
--
assignee: -> loewis
nosy: +loewis
priority: -> normal
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1081>
__
_
Sean Reifschneider added the comment:
Attached a patch which I *THINK* fixes this, but I don't run Windows.
Can someone else check this?
--
assignee: -> lemburg
nosy: +jafo, lemburg
priority: -> normal
__
Tracker <[EMAIL PRO
Changes by Sean Reifschneider:
--
assignee: -> aimacintyre
nosy: +aimacintyre
priority: -> normal
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Changes by Sean Reifschneider:
--
assignee: -> gvanrossum
nosy: +gvanrossum
priority: -> low
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1004>
__
Sean Reifschneider added the comment:
Supplied patch passes "make test", BTW.
--
keywords: +patch
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1082>
__
Changes by Sean Reifschneider:
--
priority: -> normal
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1027>
__
___
Python-bugs-list mailing list
Uns
Sean Reifschneider added the comment:
NOTE: See also issue1032 which has a patch for this.
Can we come to a consensus on which one has the best patch?
--
assignee: -> loewis
nosy: +jafo, loewis
_
Tracker <[EMAIL PROTECTED]>
<http://bug
Changes by Sean Reifschneider:
--
assignee: -> loewis
nosy: +loewis
priority: -> normal
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1032>
__
_
Changes by Sean Reifschneider:
--
priority: -> low
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1047>
__
___
Python-bugs-list mailing list
Uns
Changes by Sean Reifschneider:
--
assignee: -> georg.brandl
priority: -> normal
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1061>
__
__
Changes by Sean Reifschneider:
--
priority: -> normal
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1086>
__
___
Python-bugs-list mailing list
Uns
Changes by Sean Reifschneider:
--
assignee: -> gvanrossum
priority: -> low
resolution: -> remind
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.py
Changes by Sean Reifschneider:
--
assignee: -> tim_one
nosy: +tim_one
priority: -> normal
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1045>
__
_
Changes by Sean Reifschneider:
--
assignee: -> georg.brandl
priority: -> low
severity: urgent -> normal
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.py
Changes by Sean Reifschneider:
--
priority: -> normal
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1102>
__
___
Python-bugs-list mailing list
Uns
Changes by Sean Reifschneider:
--
assignee: -> loewis
priority: -> normal
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1110>
__
___
Python-bugs
Changes by Sean Reifschneider:
--
assignee: -> loewis
nosy: +loewis
priority: -> low
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1115>
__
__
Changes by Sean Reifschneider:
--
priority: -> normal
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1104>
__
___
Python-bugs-list mailing list
Uns
Changes by Sean Reifschneider:
--
priority: -> normal
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1034>
__
___
Python-bugs-list mailing list
Uns
Changes by Sean Reifschneider:
--
assignee: -> gvanrossum
nosy: +gvanrossum
priority: -> normal
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1109>
__
Changes by Sean Reifschneider:
--
priority: -> normal
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1005>
__
___
Python-bugs-list mailing list
Uns
Changes by Sean Reifschneider:
--
priority: -> normal
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1002>
__
___
Python-bugs-list mailing list
Uns
Changes by Sean Reifschneider:
--
assignee: -> tim_one
nosy: +tim_one
priority: -> normal
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1108>
__
_
Changes by Sean Reifschneider:
--
assignee: -> gvanrossum
nosy: +gvanrossum
priority: -> normal
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1014>
__
Changes by Sean Reifschneider:
--
priority: -> normal
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1128>
__
___
Python-bugs-list mailing list
Uns
Changes by Sean Reifschneider:
--
priority: -> low
severity: normal -> minor
status: open -> pending
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.py
Sean Reifschneider added the comment:
This is a documentation complaint, right? Perhaps more of a discussion
of why not implement these attributes on file-like objects. In general,
I believe the documentation is correct. Setting fileno to -1 is likely
to break other things in unexpected ways
Sean Reifschneider added the comment:
Can I get more information about how to reproduce this? What is it you
do to get to this? It sounds like you're talking about some HTML
documentation, but if I go to the current documentation in the Language
section, and click on the "for"
Changes by Sean Reifschneider:
--
assignee: -> akuchling
nosy: +akuchling
priority: -> normal
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1137>
__
Changes by Sean Reifschneider:
--
assignee: -> akuchling
components: +Library (Lib) -Extension Modules
nosy: +akuchling
priority: -> normal
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Sean Reifschneider added the comment:
Applied as revision 58179 to 2.5 maintenance branch, passes tests.
--
nosy: +jafo
priority: -> low
status: open -> closed
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Changes by Sean Reifschneider:
--
priority: -> normal
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1144>
__
___
Python-bugs-list mailing list
Uns
Changes by Sean Reifschneider:
--
priority: urgent -> normal
_
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1530559>
_
___
Python-bugs-li
Sean Reifschneider added the comment:
It's not clear to me what the next step is here, does one or more of the
other folks need to provide some input? Georg: If you are looking for
something from someone, can you assign the ticket to them?
--
assignee: -> georg.brandl
nos
Sean Reifschneider added the comment:
If I read the 2003 python-dev thready correctly, there isn't a solution
to this. Does this need to go back to python-dev, or do we just call it
"wont fix"? Or...?
--
assignee: -> tim_one
no
Sean Reifschneider added the comment:
Attached is a patch that fixes "writeable". I'm thinking, close this if
the patch looks ok, and open another for a general "identify
non-englishisms" ticket, once they're identified a ticket could be
opened to fix them.
I fixe
Changes by Sean Reifschneider:
--
priority: -> normal
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1130>
__
___
Python-bugs-list mailing list
Uns
Changes by Sean Reifschneider:
--
priority: -> low
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1019>
__
___
Python-bugs-list mailing list
Uns
Sean Reifschneider added the comment:
I believe this is just a place where the documentation could be cleared
up. Seems to me the confusion is from the document saying
(paraphrased): "white space is removed from both ends".
Perhaps it should say something like "runs of 1 or more
Changes by Sean Reifschneider:
--
status: open -> closed
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1150>
__
___
Python-bugs-list mailing li
Sean Reifschneider added the comment:
Comitted as revision 58182, with additional change mentioned by Guido.
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/
Sean Reifschneider added the comment:
Attached is a patch that fixes uname() instead of the individual
helpers. I agree that is the better way to do it. Again, not tested on
Windows because I don't have it.
What about adding a "isWindows()" sort of method that does the
Sean Reifschneider added the comment:
I'm thinking that nirs is not thinking of this in the "duck typing"
environment. Duck typing says that you implement things that are
appropriate for your object type, and code does what it needs to do. If
the object doesn't support attr
Sean Reifschneider added the comment:
Shall I commit my "v2" patch then, to 2.5.2 and trunk? It has the code
in the uname() method, as you say.
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.p
Changes by Sean Reifschneider:
--
versions: +Python 2.6
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1082>
__
___
Python-bugs-list mailing list
Unsubs
Sean Reifschneider added the comment:
Commited in trunk revision 58183 and 25-maint revision 58184.
--
resolution: -> accepted
status: open -> closed
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Sean Reifschneider added the comment:
I don't know anything about the .chm file. Fred: Do you know where this
comes from?
--
assignee: jafo -> fdrake
nosy: +fdrake
status: pending -> open
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.
Sean Reifschneider added the comment:
I do not believe this is a Python problem but instead a problem with
your code. I believe the problem is likely that you still have a copy
of the stdout is open, the fork that is reading also gets associated
with that same file. I can't point you a
Sean Reifschneider added the comment:
I'm closing this because the slow I/O issue is known and expected to be
resolved as part of the Python 3.0 development. The Windows problems
with missing lines should be opened as a separate issue.
--
nosy: +jafo
resolution: -> duplicat
Changes by Sean Reifschneider:
--
priority: -> normal
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1155>
__
___
Python-bugs-list mailing list
Uns
Changes by Sean Reifschneider:
--
assignee: -> jafo
components: +Tests
nosy: +jafo
priority: -> normal
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Changes by Sean Reifschneider:
--
priority: -> normal
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1151>
__
___
Python-bugs-list mailing list
Uns
Changes by Sean Reifschneider:
--
priority: -> normal
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1161>
__
___
Python-bugs-list mailing list
Uns
Changes by Sean Reifschneider:
--
priority: -> normal
resolution: -> postponed
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1159>
__
___
Python
Changes by Sean Reifschneider:
--
priority: -> normal
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1083>
__
___
Python-bugs-list mailing list
Uns
Changes by Sean Reifschneider:
--
priority: -> normal
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1163>
__
___
Python-bugs-list mailing list
Uns
Sean Reifschneider added the comment:
I can verify that on Red Hat 7 Python 2.5 that the test does fail and
the patch resolves it.
--
nosy: +jafo
priority: -> normal
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.o
Changes by Sean Reifschneider:
--
priority: -> normal
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1099>
__
___
Python-bugs-list mailing list
Uns
Changes by Sean Reifschneider:
--
nosy: -jafo
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1135>
__
___
Python-bugs-list mailing list
Unsubs
Changes by Sean Reifschneider:
--
assignee: -> nnorwitz
nosy: +nnorwitz
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1134>
__
___
Python-bugs-li
Sean Reifschneider added the comment:
Confirmed problem (used 4.5GB before I killed it), and that the second
patch resolved the problem. I'm uploading the inline patch as an
attachment, with the directory name in it as well (from svn diff).
Bumping the priority to high because the
Changes by Sean Reifschneider:
--
assignee: jafo -> nobody
nosy: +nobody
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1157>
__
___
Python-bugs-li
Changes by Sean Reifschneider:
--
priority: -> normal
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1167>
__
___
Python-bugs-list mailing list
Uns
Changes by Sean Reifschneider:
--
assignee: -> georg.brandl
nosy: +georg.brandl
priority: -> normal
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Sean Reifschneider added the comment:
Doesn't the exception count as warning the user?
We probably don't want to change readline to return a partial line in
this case. An exception could be added for EGAIN that includes the
partial line. Another option would be to just document th
Changes by Sean Reifschneider:
--
priority: -> normal
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1170>
__
___
Python-bugs-list mailing list
Uns
Changes by Sean Reifschneider:
--
assignee: -> gvanrossum
keywords: +patch, py3k
nosy: +gvanrossum
priority: -> normal
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Sean Reifschneider added the comment:
Patch looks good to me. Fred?
Comments on "should I do more fixes": Just straight documentation
changes are, in my experience, fairly likely to be processed quickly.
Changes to the code may take quite a lot more discussion. Smaller,
individu
Sean Reifschneider added the comment:
Why are you putting the file in non-blocking mode? Why not just reading
in blocking mode? If you want to do other work when a line is not
available, you could use select to check to see if there's data ready
via a small or 0 ti
Changes by Sean Reifschneider:
--
priority: -> normal
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1176>
__
___
Python-bugs-list mailing list
Uns
Sean Reifschneider added the comment:
Facundo: Should this be closed?
--
nosy: +jafo
priority: -> normal
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.o
Sean Reifschneider added the comment:
Arguably, you should be using "select" and "read" (instead of readline)
for this operation. That's what I've done in the past when doing
something similar. Specifically, I believe I have looped reading into a
buffer with
1 - 100 of 316 matches
Mail list logo
