[issue1624] Remove output comparison for test_pep277
New submission from Brett Cannon: The output from test_pep277.py seems to be completely worthless in terms of testing. The attached patch removes the output comparison file from Lib/test/output and changes test_pep277.py to not output anything. But since I don't have a Windows box I can't test this patch to commit it myself. -- components: Tests files: rm_output-test_pep277.diff messages: 58618 nosy: brett.cannon priority: low severity: normal status: open title: Remove output comparison for test_pep277 type: behavior versions: Python 2.6 Added file: http://bugs.python.org/file8952/rm_output-test_pep277.diff __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1624 __ rm_output-test_pep277.diff Description: Binary data ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1625] bz2.BZ2File doesn't support multiple streams
New submission from Thomas Herve: The BZ2File class only supports one stream per file. It possible to have multiple streams concatenated in one file, it the resulting data should be the concatenation of all the streams. It's what the bunzip2 program produces, for example. It's also supported by the gzip module. Once this done, this would add the ability to open a file for appending, by adding another stream to the file. I'll probably try to do this, but the fact it's done in C (unlike gzip) makes it harder, so if someone beats me to it, etc. -- components: Library (Lib) messages: 58619 nosy: therve severity: normal status: open title: bz2.BZ2File doesn't support multiple streams type: rfe versions: Python 2.6 __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1625 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1621] Python should compile with -Wstrict-overflow when using gcc
Changes by Marc-Andre Lemburg: -- nosy: -lemburg __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1621 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1621] Python should compile with -Wstrict-overflow when using gcc
Marc-Andre Lemburg added the comment: Whatever you change regarding the compiler options for Python, please make sure that this doesn't effect the default settings used by distutils to compile external modules (it normally takes the options straight from the Makefile used for compiling Python). Otherwise, you're likely going to break lots and lots of extensions. Thanks. -- nosy: +lemburg __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1621 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1623] Implement PEP-3141 for Decimal
Changes by Christian Heimes: -- assignee: - facundobatista keywords: +patch, py3k nosy: +facundobatista priority: - normal __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1623 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1602] windows console doesn't print utf8 (Py30a2)
Mark Summerfield added the comment: I've looked into this a bit more, and from what I can see, code page 65001 just doesn't work---so it is a Windows problem not a Python problem. A possible solution might be to read/write UTF16 which managed Windows applications can do. __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1602 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1627] Problem with httplib and Content-Length: -1
New submission from Álvaro Iradier:
When opening an IP Webcam URL with urllib2, the response is a continuous
secuence of Jpeg files from the server, preceded by the following headers:
Server: DM-Web
Content-type:
multipart/x-mixed-replace;boundary=0plm(Pico-Web:Server-Push:Boundary-String)1qaz
Content-length: -1
As you can see, the Content-Type is multipart/x-mixed-replace, and the
Content-Length reported by the server is '-1', which is strange (I guess
it would be better not to report Content-Length)
The problem is trying to read anything from the file-like object
returned by urlopen will block forever. Problem seems to be here, in
httplib.py, class HTTPResponse, method 'begin':
...
# will the connection close at the end of the response?
self.will_close = self._check_close()
# do we have a Content-Length?
# NOTE: RFC 2616, S4.4, #3 says we ignore this if tr_enc is
chunked
length = self.msg.getheader('content-length')
if length and not self.chunked:
try:
self.length = int(length)
except ValueError:
self.length = None
else:
self.length = None
...
The length attribute is being set to '-1' which leads to blocking when
reading from the endless stream of data. (See the read method in class
_fileobject, socket.py).
I don't know if this is the right fix, but I would suggest changing:
length = self.msg.getheader('content-length')
if length and not self.chunked:
to:
length = self.msg.getheader('content-length')
if length = 0 and not self.chunked:
--
components: Library (Lib)
messages: 58624
nosy: airadier
severity: major
status: open
title: Problem with httplib and Content-Length: -1
type: behavior
versions: Python 2.5
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1627
__
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1623] Implement PEP-3141 for Decimal
Mark Dickinson added the comment: I think you probably don't want to use quantize here: it makes use of the current context, which means (for example) that trunc(Decimal(integer_with_30_digits)) will fail with an InvalidOperation exception. I assume what's wanted is something that operates purely on Decimals and is unaffected by the context. Is this true? -- nosy: +marketdickinson __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1623 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1626] threading.Thread objects are not reusable after join()
Sebastien BRACQUEMONT added the comment:
Hi Amaury,
to me,Thread objects are meant to be abstract representation of a processing
that will occur in a separate execution unit at thread start time.
Indeed, that's what the following text (from the link you provided tries to
explain)
Once a thread object is created, its activity must be started by calling the
thread’s start() method. This invokes the run() method in a separate thread of
control.
So, the 'System Thread' is only created at start() call (which is a good
implementation choice)
Moreover, the join() method (when completed) will wait for the System Thread to
be disallocated.
However, the Thread object instance and the processing bound to it are still
valid.
So in an object oriented point of view, (and syntactically too) , it should be
valid to reuse the object (and so repeat the processing bound to it) as many
times as necessary without the need to create a new instance as long as the
Thread object state is not Alive.
What suprises me , is that the current implementation of threading.Thread
(apart from the __started flag behaviour) is compatible with that point of view
and i see no limitations (apart that bug) preventing such a use of threads.
I think the threading API will provide better 'high-level' view if it didn't
depend on low level considerations (as the dependency on the existence /
reusability of the peer System Thread that will be used to effectively host the
code execution)
Regards,
Sebastien
_
Express yourself instantly with MSN Messenger! Download today it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
Added file: http://bugs.python.org/file8953/unnamed
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1626
__html
head
style
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
/style
/head
body class='hmmessage'Hi Amaury,BR
nbsp;BR
to me,Thread objects are meant to be STRONGabstract/STRONG representation
of a processing that will occur in a separate execution unit at thread start
time.BR
Indeed, that's what the following text (from the link you provided tries to
explain)BR
nbsp;BR
Once a thread object is created, its activity must be started by calling the
threadâs TT class=xref docutils literalSPAN
class=prestart()/SPAN/TT method. This invokes the TT class=xref docutils
literalSPAN class=prerun()/SPAN/TT method in a separate thread of
control.BR
nbsp;BR
So, the 'System Thread' is only creatednbsp;at start() call (which is a good
implementation choice)BR
Moreover, the join() method (when completed) will wait for the System Thread to
be disallocated.BR
nbsp;BR
However,nbsp;the Thread object instance and the processing bound to it are
still valid.BR
nbsp;BR
So in an object oriented point of view, (and syntactically too)nbsp;, it
should be valid to reuse the object (and so repeat the processing bound to it)
as many times as necessary without the need to create a new instance as long as
the Thread object state is not Alive.BR
nbsp;BR
What suprises me , is that the current implementationnbsp; of threading.Thread
(apart from the __started flag behaviour) is compatible with that point of view
and i see no limitations (apart that bug) preventing such a use of threads.BR
nbsp;BR
I think the threading API will provide better 'high-level' view if it didn't
depend on low level considerations (as the dependency on the existence /
reusability of the peer System Thread that will be used to effectively host the
code execution)BR
nbsp;BR
Regards,BR
nbsp;BR
SebastienBRBRBRBR
HR id=stopSpelling
BR
gt; Subject: [issue1626] threading.Thread objects are not reusable after
join()BRgt; To: [EMAIL PROTECTED]BRgt; From: [EMAIL PROTECTED]BRgt;
Date: Fri, 14 Dec 2007 13:03:54 +BRgt; BRgt; BRgt; Amaury Forgeot
d'Arc added the comment:BRgt; BRgt; From the documentation:BRgt;
http://docs.python.org/dev/library/threading.html#threading.Thread.startBRgt;
start() must be called at most once per thread object.BRgt; BRgt; I
think this will not change: when a system thread terminates, youBRgt; cannot
restart it; you have to create another thread.BRgt; The same argument
applies to threading.Thread. It would be surprisingBRgt; that this object
can represent multiple system threads.BRgt; BRgt; You should create and
start different Threads each time.BRgt; BRgt; --BRgt; nosy:
+amaury.forgeotdarcBRgt; resolution: -gt; invalidBRgt; status: open
-gt; closedBRgt; BRgt; __BRgt;
Tracker lt;[EMAIL PROTECTED]gt;BRgt;
lt;http://bugs.python.org/issue1626gt;BRgt;
__BRBRbr /hr /Express yourself
instantly with MSN Messenger! a
href='http://clk.atdmt.com/AVE/go/onm00200471ave/direct/01/' target='_new'MSN
Messenger/a/body
/html
[issue1628] test_distutils unit test is failing rev:59499
New submission from Joseph Armbruster: Error detailed below.. I reverted the changes to sysconfig.py from rev 59488 and the error goes away. I believe the suspect line is: # head python_build = os.path.isfile(os.path.join(project_base, Modules, Setup.local)) # after revert python_build = os.path.isfile(os.path.join(project_base, Modules, Setup.dist)) D:\work\py trunk\PCbuild9rt test_distutils Deleting .pyc/.pyo files ... 92 .pyc deleted, 0 .pyo deleted D:\work\py trunk\PCbuild9python -E -tt ../lib/test/regrtest.py test_distutils test_distutils test test_distutils failed -- Traceback (most recent call last): File D:\work\py trunk\lib\distutils\tests\test_sysconfig.py, line 16, in test_get_config_h_filename self.assert_(os.path.isfile(config_h), config_h) AssertionError: D:\work\py trunk\include\pyconfig.h 1 test failed: test_distutils About to run again without deleting .pyc/.pyo first: Press any key to continue . . . -- components: Distutils messages: 58626 nosy: JosephArmbruster, tiran severity: normal status: open title: test_distutils unit test is failing rev:59499 versions: Python 3.0 __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1628 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1626] threading.Thread objects are not reusable after join()
New submission from Sebastien BRACQUEMONT: After a call to join() method on a Threading.thread object,there is no way to successfully call start() method on it. Indeed, the __started flag is not reset in the theading.Thread join() method. Since the start() method checks for __started flag , this flag is always true after a first start, despite the thread was effectively stopped by the join() call Since it's perfectly legal to store a threading.Thread object in a variable or an object member, i think the join() behaviour is odd because it prevents instance reusability. -- components: Library (Lib) messages: 58622 nosy: dweeves severity: normal status: open title: threading.Thread objects are not reusable after join() type: behavior versions: Python 2.4, Python 2.5 __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1626 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1623] Implement PEP-3141 for Decimal
Mark Dickinson added the comment: Sorry: that was nonsense. trunc is fine---it's round, floor and ceil that fail on large arguments with this patch: import decimal, math math.floor(decimal.Decimal(1e30)) Traceback (most recent call last): File stdin, line 1, in module File /Users/dickinsm/python_source/py3k/Lib/decimal.py, line 1475, in __floor__ return trunc(self.quantize(Decimal(1), rounding=ROUND_FLOOR)) File /Users/dickinsm/python_source/py3k/Lib/decimal.py, line 2265, in quantize 'quantize result has too many digits for current context') File /Users/dickinsm/python_source/py3k/Lib/decimal.py, line 3546, in _raise_error raise error(explanation) decimal.InvalidOperation: quantize result has too many digits for current context round(decimal.Decimal(1e30)) Traceback (most recent call last): File stdin, line 1, in module File /Users/dickinsm/python_source/py3k/Lib/decimal.py, line 1487, in __round__ return trunc(self.quantize(Decimal(1), rounding=ROUND_HALF_EVEN)) File /Users/dickinsm/python_source/py3k/Lib/decimal.py, line 2265, in quantize 'quantize result has too many digits for current context') File /Users/dickinsm/python_source/py3k/Lib/decimal.py, line 3546, in _raise_error raise error(explanation) decimal.InvalidOperation: quantize result has too many digits for current context Can I suggest using _rescale instead of quantize? For example, def __round__(self, ndigits:_numbers.Integral=None): Rounds self to ndigits decimal places, defaulting to 0. If ndigits is omitted or None, returns an int, otherwise a Decimal. Rounds half toward even. if ndigits is None: return trunc(self._rescale(0, rounding=ROUND_HALF_EVEN)) return self._rescale(-ndigits, rounding=ROUND_HALF_EVEN) __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1623 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1626] threading.Thread objects are not reusable after join()
Amaury Forgeot d'Arc added the comment: From the documentation: http://docs.python.org/dev/library/threading.html#threading.Thread.start start() must be called at most once per thread object. I think this will not change: when a system thread terminates, you cannot restart it; you have to create another thread. The same argument applies to threading.Thread. It would be surprising that this object can represent multiple system threads. You should create and start different Threads each time. -- nosy: +amaury.forgeotdarc resolution: - invalid status: open - closed __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1626 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1469] SSL tests leak memory
Bill Janssen added the comment: The server isn't handling the close event properly. I'll fix that. On Dec 13, 2007 9:06 PM, Guido van Rossum [EMAIL PROTECTED] wrote: Guido van Rossum added the comment: I spoke too soon. In a debug build, this hangs forever during the second iteration: ./python.exe Lib/test/regrtest.py -uall -R1:1 test_ssl Adding -v, it looks like two iterations are carried out perfectly (one must be a trial run, one the warm-up run), but the third run goes beserk; the output ends like this: testAsyncoreServer (test.test_ssl.ThreadedTests) ... server: read b'over\n' from client server: closed connection ssl.SSLSocket object, fd=6, family=2, type=1, proto=0 server: read b'' from client server: closed connection ssl.SSLSocket object, fd=10, family=2, type=1, proto=0 server: read b'' from client server: closed connection ssl.SSLSocket object, fd=10, family=2, type=1, proto=0 . . (the last two lines repeated forever) . __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1469 __ Added file: http://bugs.python.org/file8954/unnamed __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1469 __The server isn#39;t handling the close event properly.nbsp; I#39;ll fix that.brbrdiv class=gmail_quoteOn Dec 13, 2007 9:06 PM, Guido van Rossum lt;a href=mailto:[EMAIL PROTECTED][EMAIL PROTECTED]/agt; wrote: brblockquote class=gmail_quote style=border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;div class=Ih2E3dbrGuido van Rossum added the comment:brbr/divI spoke too soon. In a debug build, this hangs forever during the brsecond iteration:brbr./python.exe Lib/test/regrtest.py -uall -R1:1 test_sslbrbrAdding -v, it looks like two iterations are carried out perfectly (onebrmust be a trial run, one the warm-up run), but the third run goes brbeserk; the output ends like this:brdiv class=Ih2E3dbrtestAsyncoreServer (test.test_ssl.ThreadedTests) ...br/divnbsp;server: nbsp;read b#39;over\n#39; from clientbrnbsp;server: nbsp;closed connection lt;ssl.SSLSocket object, fd=6, family=2,brtype=1, proto=0gt;brnbsp;server: nbsp;read b#39;#39; from clientbrnbsp;server: nbsp;closed connection lt;ssl.SSLSocket object, fd=10, family=2,brtype=1, proto=0gt;brnbsp;server: nbsp;read b#39;#39; from client brnbsp;server: nbsp;closed connection lt;ssl.SSLSocket object, fd=10, family=2,brtype=1, proto=0gt;br.br. (the last two lines repeated forever)brdivdiv/divdiv class=Wj3C7c.brbr__ brTracker lt;a href=mailto:[EMAIL PROTECTED][EMAIL PROTECTED]/agt;brlt;a href=http://bugs.python.org/issue1469; target=_blankhttp://bugs.python.org/issue1469/agt;br__ br/div/div/blockquote/divbr ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1469] SSL tests leak memory
Bill Janssen added the comment: Here's an update version where the asyncore test server properly handles the EOF race condition. Added file: http://bugs.python.org/file8955/patch-4 __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1469 __ patch-4 Description: Binary data ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1469] SSL tests leak memory
Changes by Bill Janssen: Removed file: http://bugs.python.org/file8949/patch-3 __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1469 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1469] SSL tests leak memory
Changes by Bill Janssen: Removed file: http://bugs.python.org/file8954/unnamed __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1469 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1626] threading.Thread objects are not reusable after join()
Martin v. Löwis added the comment: I agree with Amaury. This all works exactly as it should work, and will not change. -- nosy: +loewis __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1626 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1624] Remove output comparison for test_pep277
Guido van Rossum added the comment: Crys, can you look into this? -- assignee: - tiran keywords: +patch nosy: +gvanrossum, tiran __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1624 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1628] test_distutils unit test is failing rev:59499
Changes by Guido van Rossum: -- assignee: - tiran priority: - high __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1628 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1469] SSL tests leak memory
Guido van Rossum added the comment: Here's an update version where the asyncore test server properly handles the EOF race condition. Perfect! Check it in. __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1469 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1629] Py_Size() should be named Py_SIZE()
New submission from Raymond Hettinger: It would be helpful to have the name provide a cue that a macro is being used. -- assignee: loewis components: Extension Modules messages: 58634 nosy: loewis, rhettinger severity: normal status: open title: Py_Size() should be named Py_SIZE() versions: Python 2.6 __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1629 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1629] Py_Size() should be named Py_SIZE()
Guido van Rossum added the comment: Agreed. -- nosy: +gvanrossum __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1629 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1629] Py_Size() should be named Py_SIZE()
Martin v. Löwis added the comment: I assume that applies to Py_Refcnt and Py_Type as well? __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1629 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1629] Py_Size() should be named Py_SIZE()
Christian Heimes added the comment: I think it would be easier to merge from trunk to py3k before the change and skip the revision in the next merge. The rename can be done with a simple find | xargs sed -i. A merge might be more painful. -- nosy: +tiran __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1629 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1469] SSL tests leak memory
Bill Janssen added the comment: Done. On Dec 14, 2007 9:44 AM, Guido van Rossum [EMAIL PROTECTED] wrote: Guido van Rossum added the comment: Here's an update version where the asyncore test server properly handles the EOF race condition. Perfect! Check it in. __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1469 __ Added file: http://bugs.python.org/file8956/unnamed __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1469 __Done.brbrdiv class=gmail_quoteOn Dec 14, 2007 9:44 AM, Guido van Rossum lt;a href=mailto:[EMAIL PROTECTED][EMAIL PROTECTED]/agt; wrote:brblockquote class=gmail_quote style=border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex; brGuido van Rossum added the comment:brdiv class=Ih2E3dbrgt; Here#39;s an update version where the asyncore test server properly handlesbrgt; the EOF race condition.brbr/divPerfect! Check it in.brdiv div/divdiv class=Wj3C7cbr__brTracker lt;a href=mailto:[EMAIL PROTECTED][EMAIL PROTECTED]/agt;brlt;a href=http://bugs.python.org/issue1469; target=_blank http://bugs.python.org/issue1469/agt;br__br/div/div/blockquote/divbr ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1469] SSL tests leak memory
Changes by Guido van Rossum: -- resolution: - fixed status: open - closed __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1469 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1609] test_re.py fails
Ismail Donmez added the comment: Any ideas/comments on how to move forward with this? Thanks, ismail __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1609 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1610] test_socket.py fails
Ismail Donmez added the comment: Any other thing I can do to debug this? __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1610 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1350] IDLE - CallTips enhancement - show full doc-string in new window
Tal Einat added the comment: Alrighty then! Since I had also done some work on CallTips.py since the previous patch, I've worked up a merged version, including stuff from the py3k version and better tests. Changes since the first patch: * add support for callable instances (e.g. __call__) * use inspect, which does the hackish stuff for us, such as using object.im_func where needed and formatting doc-strings appropriately * use isinstance instead of type checking, like in the py3k branch * rename get_arg_text to get_arg_text_and_doc * add test cases for callable instances, classmethods, staticmethods and old-style classes * rework testing code * tested extensively (only on WinXP, Python2.5) I'm attaching a patch relative to the current SVN head, and another one relative to the current SVN head with the previous patch applied. Added file: http://bugs.python.org/file8957/IDLE_CallTips.071214.patch __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1350 __ IDLE_CallTips.071214.patch Description: Binary data ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1350] IDLE - CallTips enhancement - show full doc-string in new window
Changes by Tal Einat: Added file: http://bugs.python.org/file8958/IDLE_CallTips.071214.incremental.patch __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1350 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1350] IDLE - CallTips enhancement - show full doc-string in new window
Tal Einat added the comment: Now for CallTipWindow.py: * split conditionals into two lines as requested * changed the test (took me a while to understand what controversy you were referring to...) I couldn't find anything wrong with the first line. It is the function/method signature if it was found, or just the beginning of the doc-string otherwise. Unless you think the adding the signature (when possible) is unnecessary/confusing... The above changes are included in both new patches. Added file: http://bugs.python.org/file8959/IDLE_CallTips.071214.patch __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1350 __ IDLE_CallTips.071214.patch Description: Binary data ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1350] IDLE - CallTips enhancement - show full doc-string in new window
Changes by Tal Einat: Added file: http://bugs.python.org/file8960/IDLE_CallTips.071214.incremental.patch __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1350 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1350] IDLE - CallTips enhancement - show full doc-string in new window
Tal Einat added the comment: (bah, sorry for the mess, use the patch files from the later hour) __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1350 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1607] Patch for TCL 8.5 support
Changes by Tal Einat: -- nosy: +taleinat __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1607 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1630] sys.maxint is documented but should not be
Christian Heimes added the comment: Thanks for the bug report I fixed the problem in r59518 -- keywords: +py3k nosy: +tiran resolution: - fixed status: open - closed __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1630 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1630] sys.maxint is documented but should not be
New submission from Blair Zajac:
There is still documentation for sys.maxint even though it no
longer exists in Python 3.0:
$ /tmp/p3.0/bin/python
Python 3.0a2 (r30a2:59382, Dec 13 2007, 11:07:38)
[GCC 3.4.3 20050227 (Red Hat 3.4.3-22.1)] on linux2
Type help, copyright, credits or license for more information.
import sys
[x for x in sys.__doc__.split('\n') if x.find('maxint') != -1]
['maxint -- the largest supported integer (the smallest is -maxint-1)']
sys.maxint
Traceback (most recent call last):
File stdin, line 1, in module
AttributeError: 'module' object has no attribute 'maxint'
--
components: Library (Lib)
messages: 58645
nosy: blair
severity: normal
status: open
title: sys.maxint is documented but should not be
versions: Python 3.0
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1630
__
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1631] Send output from subprocess.Popen objects to any object with a write() method
New submission from Nishkar Grover:
It would be nice if we could send output from subprocess.Popen objects
to any object with a write() method.
Consider the following example, where I'm using Python 2.4.4 (#1, Jun 28
2007, 15:10:17, GCC 3.4.3 on linux2)...
fh = open('/tmp/file.txt', 'w')
cmdObj = subprocess.Popen('uname -a', shell=True, stdout=fh)
fh.close()
fh = open('/tmp/file.txt', 'r')
fh.read()
'Linux northstar 2.6.9-42.0.2.IT111843.1.ELsmp #1 SMP Fri May 11
18:50:54 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux\n'
That demonstrates that I can successfully send the stdout output from my
subprocess.Popen object to a file handle.
I tried to send that output to a custom object that has a write() method...
class Foo(object):
... def write(self, msg):
... sys.stdout.write('*** %s ***' % msg.rstrip() + os.linesep)
... sys.stdout.flush()
... def close(self):
... pass
...
foo = Foo()
cmdObj = subprocess.Popen('uname -a', shell=True, stdout=foo)
Traceback (most recent call last):
File stdin, line 1, in ?
File /rel/lang/python/2.4.4-4/lib/python2.4/subprocess.py, line 534,
in __init__
(p2cread, p2cwrite,
File /rel/lang/python/2.4.4-4/lib/python2.4/subprocess.py, line 840,
in _get_handles
c2pwrite = stdout.fileno()
AttributeError: 'Foo' object has no attribute 'fileno'
so I gave it a fileno() method that returns None...
class Foo(object):
... def write(self, msg):
... sys.stdout.write('*** %s ***' % msg.rstrip() + os.linesep)
... sys.stdout.flush()
... def close(self):
... pass
... def fileno(self):
... return None
...
foo = Foo()
cmdObj = subprocess.Popen('uname -a', shell=True, stdout=foo)
Linux northstar 2.6.9-42.0.2.IT111843.1.ELsmp #1 SMP Fri May 11
18:50:54 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux
Notice that the output went straight to the console and bypassed my
'foo' object's write() method.
--
components: Library (Lib)
messages: 58646
nosy: ngrover
severity: normal
status: open
title: Send output from subprocess.Popen objects to any object with a write()
method
type: behavior
versions: Python 2.4
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1631
__
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1631] Send output from subprocess.Popen objects to any object with a write() method
Christian Heimes added the comment: It's not going to be easy and there is also no point to implement the feature. The subprocess module requires either a real file or a PIPE. A real file is needed because the subprocess module uses some low level operation system functions for speed efficiency. It writes data directly to a file descriptor (the number returned by fileno()). In your case it seems have to interpreted None as 0 which is - by accident - the file descriptor of stdout. For small amounts of data use Popen(..., stdout=subprocess.PIPE) and use out, err = communicate([stdin]), for large amounts of data you should use a temporary file (tempfile module). In your case please use the platform module instead of uname :) -- nosy: +tiran resolution: - wont fix status: open - pending __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1631 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1607] Patch for TCL 8.5 support
Christian Heimes added the comment: Plans is exaggerated. I was merely testing Tcl 8.5. The Python 3.0a2 release has some major problems with Tcl. The Win32 version doesn't work well and I wasn't able to create a 64bit version. Do you have a Windows box to test IDLE on Windows? You can use the free VS2008 Express Edition to compile Python. __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1607 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1602] windows console doesn't print utf8 (Py30a2)
Christian Heimes added the comment: We are aware of multiple Windows related problems. We are planing to rewrite parts of the Windows specific API to use the widechar variants. Maybe that will help. -- keywords: +py3k nosy: +tiran priority: - low __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1602 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1632] email
New submission from Wubbulous: Python will not load the email module or any of its child modules. -- components: Library (Lib) messages: 58652 nosy: Wubbulous severity: major status: open title: email type: behavior versions: Python 2.5 __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1632 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1633] smtplib
New submission from Wubbulous: SMTP module returns no module named SMTP -- components: Library (Lib) messages: 58653 nosy: Wubbulous severity: normal status: open title: smtplib versions: Python 2.5 __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1633 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1633] smtplib
Wubbulous added the comment: SMTP returns that smtplib has no module SMTP __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1633 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1610] test_socket.py fails
Ismail Donmez added the comment: This was a glibc regression on my side, it can be closed as invalid. Thanks! __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1610 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1610] test_socket.py fails
Changes by Christian Heimes: -- resolution: - invalid status: open - closed __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1610 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1624] Remove output comparison for test_pep277
Christian Heimes added the comment: Fixed in r59519 with some small modifications. -- resolution: - fixed status: open - closed __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1624 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1632] email
Brett Cannon added the comment: More detail is needed than this in order to try to fix this. What error message are you getting? What OS? What exact version of Python? Is this a binary distro or a source one? Since all releases are thoroughly tested and never had any import issues with the email code chances are there is a problem with your environment and not Python. -- nosy: +brett.cannon __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1632 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1632] email cannot be imported
Changes by Brett Cannon: -- title: email - email cannot be imported __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1632 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1633] smtplib
Brett Cannon added the comment: There is no module named SMTP. See the list of modules at http://docs.python.org/modindex.html . -- nosy: +brett.cannon resolution: - invalid status: open - closed __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1633 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1634] with Statement Error generated following Tutorial
New submission from Nathan Turner: In Python Tutorial -- Section 8.7 Predefined Clean-up Action When following the with open... commands explicitly Python 2.5 will generate a Syntax Error; There's an error in you program: invalid syntax It would be nice if a foot note existed that took you to Python Reference Manual -- section 7.5 The with statement In that section it explains that in Python 2.5 you need to use from __future__ import with_statement For new users this might frustrate. -- components: Documentation messages: 58659 nosy: astral451 severity: normal status: open title: with Statement Error generated following Tutorial type: compile error versions: Python 2.5 __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1634 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1634] with Statement SyntaxError generated while following Tutorial
Changes by Nathan Turner: -- title: with Statement Error generated following Tutorial - with Statement SyntaxError generated while following Tutorial __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1634 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1634] with Statement SyntaxError generated while following Tutorial
Changes by Nathan Turner: -- severity: normal - minor __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1634 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
