[issue3519] Evaluation order example lacks suffix
Georg Brandl [EMAIL PROTECTED] added the comment: Thanks, fixed in r65591. -- resolution: - fixed status: open - closed ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3519 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3429] urllib.urlopen() return type
Georg Brandl [EMAIL PROTECTED] added the comment: Agreed. -- resolution: - works for me status: open - closed ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3429 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3522] zip() function example in tutorial
Georg Brandl [EMAIL PROTECTED] added the comment: Thanks, applied in r65592. -- resolution: - fixed status: open - closed ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3522 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3523] Reverse quotes in Python 3.0 tutorial
Georg Brandl [EMAIL PROTECTED] added the comment: Thanks, applied in r65593. -- resolution: - fixed status: open - closed ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3523 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3525] Changes to exceptions not reflected in tutorial examples.
Georg Brandl [EMAIL PROTECTED] added the comment: Thanks, applied in r65594. -- resolution: - fixed status: open - closed ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3525 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3524] IOError when attempting negative seek in file (Python 3.0 tutorial)
Georg Brandl [EMAIL PROTECTED] added the comment: Since the file is a text file, such seeking is not possible. I've now updated the whole section about files; in particular there was also an outdated description of text vs. binary mode. Committed r65595. -- resolution: - fixed status: open - closed ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3524 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3429] urllib.urlopen() return type
ThomasH [EMAIL PROTECTED] added the comment: On Fri, Aug 8, 2008 at 2:04 AM, Senthil [EMAIL PROTECTED] wrote: Senthil [EMAIL PROTECTED] added the comment: I agree with Benjamin on this issue, describing what is a File like Object is so much un-needed in Python and especially at urlopen function. Users have been able to understand and use it properly from a long time. If only it were more file-like. But, oh, it adds info() and geturl() methods which you have to string-search for to find the proper description in the prose. And, ah, the size argument of the read() method doesn't quite behave like on other file-like objects, but there you go. And, uh, by the way, you really can't use it in places where a true built-in file object is required (and I'm sure everybody knows what that means). - So much for file-like. I have no doubt that people can get along with the description as it is, because that's what they always try. My main point was that it is less approachable and breaks the usual format of a class documentation. But I see there is much agreement in keeping the status quo. ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3429 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3429] urllib.urlopen() return type
ThomasH [EMAIL PROTECTED] added the comment: Georg, you seem like a dedicated person. I'm sure you guys have thought about documenting return types of methods and functions in a standardized way, documenting classes so that you could fade in and out inherited features, and such. Where do you guys discuss general documentation issues? Is there a mailing list dedicated to Python documentation?! On Fri, Aug 8, 2008 at 8:43 AM, Georg Brandl [EMAIL PROTECTED] wrote: Georg Brandl [EMAIL PROTECTED] added the comment: Agreed. -- resolution: - works for me status: open - closed ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3429 ___ ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3429 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3270] test_multiprocessing: test_listener_client flakiness
Trent Nelson [EMAIL PROTECTED] added the comment: Jesse, thanks for capturing my e-mail thread in this issue. Can you comment on my last three paragraphs? Essentially, I think we should lock down the API and assert that Listener.address will always be a 'connectable' end-point. (i.e. not a wildcard host, 0.0.0.0, that can't be bound to by a socket, for example) This would mean raising an exception in Listener.__init__ if this invariant is violated. -- nosy: +Trent.Nelson ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3270 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1117601] os.path.exists returns false negatives in MAC environments.
Virgil Dupras [EMAIL PROTECTED] added the comment:
hsoft-dev:~ hsoft$ mkdir foobar
hsoft-dev:~ hsoft$ echo baz foobar/baz
hsoft-dev:~ hsoft$ chmod 000 foobar/baz
hsoft-dev:~ hsoft$ python
Python 2.5.2 (r252:60911, Feb 22 2008, 07:57:53)
[GCC 4.0.1 (Apple Computer, Inc. build 5363)] on darwin
Type help, copyright, credits or license for more information.
import os.path
os.path.exists('foobar/baz')
True
hsoft-dev:~ hsoft$ chmod 000 foobar
hsoft-dev:~ hsoft$ python
Python 2.5.2 (r252:60911, Feb 22 2008, 07:57:53)
[GCC 4.0.1 (Apple Computer, Inc. build 5363)] on darwin
Type help, copyright, credits or license for more information.
import os.path
os.path.exists('foobar/baz')
False
os.path.exists('foobar')
True
This seems like the correct behavior to me.
--
nosy: +vdupras
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1117601
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3270] test_multiprocessing: test_listener_client flakiness
Antoine Pitrou [EMAIL PROTECTED] added the comment: This would mean raising an exception in Listener.__init__ if this invariant is violated. If I understand the suggestion correctly, it would forbid people to listen on 0.0.0.0. I'm not sure it is the right correction for the problem. Listening on 0.0.0.0 can be handy when you are not sure which address to use; it would be better to address the problem elsewhere. IMO, the FQDN removal patch as uploaded by Jesse is simple and straight-forward enough, provided it does fix the bug. -- nosy: +pitrou ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3270 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1117601] os.path.exists returns false negatives in MAC environments.
Antoine Pitrou [EMAIL PROTECTED] added the comment: The only sane alternative to the current behaviour would be to raise an Exception from os.path.exists rather than returning False. But it would also break a lot of code, and complexify code using os.path.exists which currently doesn't need to check for exceptions. Returning True sounds completely incorrect on the other hand. If there is no other straightforward method than stat() to know if a path exists, I suggest closing this bug as wontfix. -- nosy: +pitrou ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue1117601 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue941346] AIX shared library fix
Sébastien Sablé [EMAIL PROTECTED] added the comment: Hi, I have modified a bit this patch to make it work with Python 2.5.2 (see attached patched). It is a great enhancement for Python users on AIX to be able to use a shared library instead of a static one, so I would appreciate if this feature could be integrated in trunk. We have various AIX 5.2 and 5.3 servers in the Sungard company where I work, and we could run some tests according to your instructions. It may also be possible to provide some limited access to one of those servers if needed but it would require some time and paper work. What kind of access would you need in order to validate those patchs? thanks in advance -- keywords: +patch nosy: +sable Added file: http://bugs.python.org/file11081/patch_AIX_shared.diff ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue941346 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue941346] AIX shared library fix
Antoine Pitrou [EMAIL PROTECTED] added the comment: Sébastien, what does your patch change exactly? Does it build a shared lib for Python by default? If that's the case, I'm not sure it's a good idea due to AIX's particular way of treating shared libraries; it might break e.g. when trying to embed Python in another program. (I say this while being an AIX novice, but I did have to compile Python under AIX for embedded use in another third-party software... unfortunately right now I don't have access to an AIX machine with a compiler) -- nosy: +pitrou ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue941346 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3526] Customized malloc implementation on SunOS and AIX
New submission from Sébastien Sablé [EMAIL PROTECTED]: Hi, We run a big application mostly written in Python (with Pyrex/C extensions) on different systems including Linux, SunOS and AIX. The memory footprint of our application on Linux is fine; however we found that on AIX and SunOS, any memory that has been allocated by our application at some stage will never be freed at the system level. After doing some analysis (see the 2 attached pdf documents), we found that this is linked to the implementation of malloc on those various systems: The malloc used on Linux (glibc) is based on dlmalloc as described in this document: http://g.oswego.edu/dl/html/malloc.html This implementation will use sbrk to allocate small chunks of memory, but it will use mmap to allocate big chunks. This ensures that the memory will actually get freed when free is called. AIX and Sun have a more naive malloc implementation, so that the memory allocated by an application through malloc is never actually freed until the application leaves (this behavior has been confirmed by some experts at IBM and Sun when we asked them for some feedback on this problem - there is a 'memory disclaim' option on AIX but it is disabled by default as it brings some major performance penalities). For long running Python applications which may allocate a lot of memory at some stage, this is a major drawback. In order to bypass this limitation of the system on AIX and SunOS, we have modified Python so that it will use the customized malloc implementation dlmalloc like in glibc (see attached patch) - dlmalloc is released in the public domain. This patch adds a --enable-dlmalloc option to configure. When activated, we observed a dramatic reduction of the memory used by our application. I think many AIX and SunOS Python users could be interested by such an improvement. -- Sébastien Sablé Sungard -- files: customized_malloc_SUN.pdf messages: 70897 nosy: sable severity: normal status: open title: Customized malloc implementation on SunOS and AIX type: resource usage Added file: http://bugs.python.org/file11082/customized_malloc_SUN.pdf ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3526 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3526] Customized malloc implementation on SunOS and AIX
Changes by Sébastien Sablé [EMAIL PROTECTED]: Added file: http://bugs.python.org/file11083/customized_malloc_AIX.pdf ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3526 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3526] Customized malloc implementation on SunOS and AIX
Changes by Sébastien Sablé [EMAIL PROTECTED]: -- keywords: +patch Added file: http://bugs.python.org/file11084/patch_dlmalloc.diff ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3526 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3270] test_multiprocessing: test_listener_client flakiness
Jesse Noller [EMAIL PROTECTED] added the comment: Unfortunately, the patch while simple, is too simple. The removal of the _address attribute breaks a lot more than it fixes (it's heavily used elsewhere) ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3270 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3527] Py_WIN_WIDE_FILENAMES removal
New submission from Hirokazu Yamamoto [EMAIL PROTECTED]: Py_WIN_WIDE_FILENAMES is not used anywhere, this patch removes this macro. -- files: remove_macro.patch keywords: patch messages: 70899 nosy: ocean-city severity: normal status: open title: Py_WIN_WIDE_FILENAMES removal versions: Python 2.5, Python 2.6, Python 3.0 Added file: http://bugs.python.org/file11085/remove_macro.patch ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3527 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2153] unittest.py modernization
Virgil Dupras [EMAIL PROTECTED] added the comment: This patch has gone invalid due to some recent conflicting changes. I remade it and I'm resubmitting it hoping that it will get applied. Added file: http://bugs.python.org/file11086/unittest_modern2.diff ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue2153 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3528] TypeError when compiling with no translator
New submission from Robert Schuppenies [EMAIL PROTECTED]:
I just ran 'make html' with the latest version and got this exception:
loading translations [en]... Exception occurred:
File /home/bob/data/dvl/python/svn/doctools/sphinx/builder.py, line
184, in load_i18n
self.info('selected locale not available' % self.config.language)
TypeError: not all arguments converted during string f
The enclosed patch fixes the issue.
--
assignee: georg.brandl
components: Documentation tools (Sphinx)
files: str_formatting.patch
keywords: patch
messages: 70901
nosy: georg.brandl, schuppenies
severity: normal
status: open
title: TypeError when compiling with no translator
type: behavior
Added file: http://bugs.python.org/file11087/str_formatting.patch
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3528
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue941346] AIX shared library fix
Sébastien Sablé [EMAIL PROTECTED] added the comment: Hum, I tried to recompile Python without the --enable-shared option on AIX and it crashed; so this patch may not be compatible with a static version of Python (though I have other patches in my version - cf issue 3526 - which may be incompatible). I will do a bit of cleanup in my environment and try to make a version of the patch that works also when compiling a static Python. ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue941346 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3270] test_multiprocessing: test_listener_client flakiness
Antoine Pitrou [EMAIL PROTECTED] added the comment: Selon Jesse Noller [EMAIL PROTECTED]: Unfortunately, the patch while simple, is too simple. The removal of the _address attribute breaks a lot more than it fixes (it's heavily used elsewhere) I don't understand what you mean. The patch you uploaded doesn't remove the _address attribute. See http://bugs.python.org/file10801/connection.patch ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3270 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3270] test_multiprocessing: test_listener_client flakiness
Jesse Noller [EMAIL PROTECTED] added the comment: I don't understand what you mean. The patch you uploaded doesn't remove the _address attribute. See http://bugs.python.org/file10801/connection.patch Hmm. Then that was a mistake on my part: it's entirely possible the patch didn't apply cleanly. I'll circle back to this shortly and re-apply/test. ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3270 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3528] TypeError when compiling with no translator
Georg Brandl [EMAIL PROTECTED] added the comment: Fixed in r65599 :-|. -- resolution: - fixed status: open - closed ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3528 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3270] test_multiprocessing: test_listener_client flakiness
Jesse Noller [EMAIL PROTECTED] added the comment: Trent/Antoine - I'm stuck on the fence about this. Per trent's own suggestion - removing the allowance for the 0.0.0.0 style address means that the self._address is always a connectable end-point: this provides clarity to the API. However - to Antoine's point - using 0.0.0.0 to listen on all addresses is actually pretty common, especially when working with bigger servers (which generally have multiple cores). Using the 0.0.0.0 address makes it easy to say listen everywhere - where, in the case of a Manager is actually very useful (you could have processes connecting to a Manager on a machine from different networks). Attached is a cleaned up diff of the removal of the fqdn call - this should resolve the original problem while leaving the door open for the ability to connect to the 0.0.0.0 address. I need someone with a windows machine (Hi Trent!) that exposed the original problem to test the patch. Currently I'm favoring this rather than locking out the 0.0.0.0 option. Added file: http://bugs.python.org/file11088/connection_v2.patch ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3270 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3270] test_multiprocessing: test_listener_client flakiness
Changes by Jesse Noller [EMAIL PROTECTED]: Removed file: http://bugs.python.org/file10801/connection.patch ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3270 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2811] doctest doesn't treat unicode literals as specified by the file declared encoding
Karen Tracey [EMAIL PROTECTED] added the comment:
I believe the problem is in your test file, not doctest. The enclosing
doctest string is not specified as a unicode literal, so the file
encoding specification ultimately has no effect on it. At least that is
how I read the documentation regarding the effect of the ecoding
declaration (The encoding is used for all lexical analysis, in
particular to find the end of a string, and to interpret the contents of
Unicode literals. String literals are converted to Unicode for
syntactical analysis, then converted back to their original encoding
before interpretation starts.)
If you change the test file so that the string enclosing the test is a
unicode literal then the test passes:
[EMAIL PROTECTED]:~/tmp$ cat test_iso-8859-15.py
# -*- coding: utf-8 -*-
import doctest
def normalize(s):
u
normalize(u'á')
u'b'
return s.translate({ord(u'á'): u'b'})
doctest.testmod()
print 'without doctest ===', normalize(u'á')
[EMAIL PROTECTED]:~/tmp$ python test_iso-8859-15.py
without doctest === b
-
There is a problem with this, though: doctest now will be unable to
correctly report errors when there are output mismatches involving
unicode strings with non-ASCII chars. For example if you add an 'x' to
the front of your unicode literal to be normalized you'll get this when
you try to run it:
[EMAIL PROTECTED]:~/tmp$ python test_iso-8859-15.py
Traceback (most recent call last):
File test_iso-8859-15.py, line 12, in module
doctest.testmod()
File /usr/lib/python2.5/doctest.py, line 1799, in testmod
runner.run(test)
File /usr/lib/python2.5/doctest.py, line 1345, in run
return self.__run(test, compileflags, out)
File /usr/lib/python2.5/doctest.py, line 1261, in __run
self.report_failure(out, test, example, got)
File /usr/lib/python2.5/doctest.py, line 1125, in report_failure
self._checker.output_difference(example, got, self.optionflags))
UnicodeEncodeError: 'ascii' codec can't encode character u'\xe1' in
position 149: ordinal not in range(128)
[EMAIL PROTECTED]:~/tmp$
This issue is reported in #1293741, but there is no fix or guidance
offered there on how to work around the problem.
I'd appreciate feedback on whether what I've said here is correct. I'm
currently trying to diagnose/fix problems with use of unicode literals
in some tests and this is as far as I've got. That is, I think I need to
be specifying the enclosing strings as unicode literals, but then I run
into #1293741. If the conclusion I've reached is correct, then trying
to figure out a fix for that problem should be where I focus my efforts.
If, however, I shouldn't be specifying the enclosing string as a
unicode literal, then attempting to fix the problem as described here
would perhaps be more useful. Though I do not know how the doctest code
can know the file's encoding specification?
--
nosy: +kmtracey
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2811
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3526] Customized malloc implementation on SunOS and AIX
Antoine Pitrou [EMAIL PROTECTED] added the comment: This is very interesting, although it should probably go through discussion on python-dev since it involves integrating a big chunk of external code. -- components: +Interpreter Core nosy: +pitrou priority: - normal versions: +Python 2.7, Python 3.1 ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3526 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3489] add rotate{left,right} methods to bytearray
Josiah Carlson [EMAIL PROTECTED] added the comment: Sadly, this isn't quite as easy as it would seem. The O(1) memory overhead version of this requires 2n reads and 2n writes, but does both reads and writes at two memory locations at a time, which may have nontrivial performance implications. The simple version that copies out the small part of the shift into a temporary buffer, doing a memcpy/memmov internally, then copying the small data back is likely to have much better performance (worst-case 1.5n reads and 1.5n writes. Offering this ability in the momoryview object would be very interesting, though I'm not sure that the memoryview object is able to offer a multi-segment buffer interface where the segments are not the same length (this could be hacked by having a single pointer per byte, but at that point we may as well perform a copy). -- nosy: +josiahcarlson ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3489 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3489] add rotate{left,right} methods to bytearray
Antoine Pitrou [EMAIL PROTECTED] added the comment:
Hi,
Sadly, this isn't quite as easy as it would seem.
You are right, I was overly optimist when thinking about this.
Offering this ability in the momoryview object would be very
interesting, though I'm not sure that the memoryview object is able to
offer a multi-segment buffer interface where the segments are not the
same length (this could be hacked by having a single pointer per byte,
but at that point we may as well perform a copy).
I'm not sure what you mean, but I think we can just restrict it to the
simple case of a single contiguous buffer.
shift{left,right} could be useful too (and faster).
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3489
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2704] IDLE: Patch to make PyShell behave more like a Terminal interface
Terry J. Reedy [EMAIL PROTECTED] added the comment: On windows: type zomeinput Press home key. In command window (terminal interface), cursor goes to just before z, where one would want. In IDLE (2.5.2, 3.0b2), it goes to beginning of line. If current patch does not fix this (there is no mention), would it be easy to add? I would expect so because the current page up places the cursor 4 chars to the right of the margin (if there is text not visible above the window to jump to and if there is text on the line jumped to). So PageUp PageDn will sometimes simulate the desired Home behavior. ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue2704 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1721083] Add File - Reload
Terry J. Reedy [EMAIL PROTECTED] added the comment: This appears to me to duplicate and supercede http://bugs.python.org/issue1175686 If so, could that be closed as superceded? -- nosy: +tjreedy ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue1721083 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3300] urllib.quote and unquote - Unicode issues
Bill Janssen [EMAIL PROTECTED] added the comment: Here's the updated version of my patch. It returns a string, but doesn't clobber bytes that are contained in the string. Naive code (basically code that expects ASCII strings from unquote) should continue to work as well as it ever did. I fixed the problem with the email library, and removed the bogus test from the http_cookiejar test suite. Added file: http://bugs.python.org/file11089/patch ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3300 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3300] urllib.quote and unquote - Unicode issues
Changes by Bill Janssen [EMAIL PROTECTED]: Removed file: http://bugs.python.org/file11064/patch ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3300 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3493] No Backslash (\) in IDLE 1.2.2
Terry J. Reedy [EMAIL PROTECTED] added the comment: \ works fine for me and I suspect almost everyone else. Please bring this up on comp.lang.python or python-list or gmane.comp.python.general to see if any other Macbook users have this problems or any ideas on what might be wrong with your particular installation. -- nosy: +tjreedy ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3493 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3489] add rotate{left,right} methods to bytearray
Josiah Carlson [EMAIL PROTECTED] added the comment: In order for MemoryView to know what bytes it is pointing to in memory, it (generally) keeps a pointer with a length. In order to rotate the data without any copies, you need a pointer and length for each rotation plus the original. For example, the equivalent to a rotate left of 8 characters using slicing is... x[8:] + x[:8]. That is two segments. That's a multi-segment buffer interface. But typical multi-segment buffer interfaces require each segment to be exactly the same length (like numpy), which is not the case with rotations. ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3489 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3489] add rotate{left,right} methods to bytearray
Antoine Pitrou [EMAIL PROTECTED] added the comment: Le vendredi 08 août 2008 à 21:44 +, Josiah Carlson a écrit : Josiah Carlson [EMAIL PROTECTED] added the comment: In order for MemoryView to know what bytes it is pointing to in memory, it (generally) keeps a pointer with a length. In order to rotate the data without any copies, you need a pointer and length for each rotation plus the original. For example, the equivalent to a rotate left of 8 characters using slicing is... x[8:] + x[:8]. Hmm, I think it's simpler if the rotate is done in-place rather than returning a new object. Most uses of memoryviews are going to be with APIs requiring a single contiguous segment. (of course for read-only buffers it would raise an error) ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3489 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3436] csv.DictReader inconsistency
Barry A. Warsaw [EMAIL PROTECTED] added the comment: Making an existing attribute a property is a nice, API-neutral way to handle this. Let's call the inconsistency a bug and this a bug fix wink so that it's fine to add to 2.6 and 3.0 at this point. -- nosy: +barry resolution: - accepted ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3436 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2827] IDLE 3.0a5 cannot handle UTF-8
Terry J. Reedy [EMAIL PROTECTED] added the comment: 3.0b2, WinXP I cut and pasted the text above into an empty IDLE edit window, hit F5, and in the blink of an eye, both IDLE windows disappeared. No error message, no Window's error box, just gone. The pasted text was saved to the file. When I added input() statements, and ran with CPython directly, it got to the function call and then crashed. Rerunning with Idle with input() at the top, it still crashed, indicating that it crashed during compilation and never started execution. -- nosy: +tjreedy ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue2827 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2983] Ttk support for Tkinter
Brett Cannon [EMAIL PROTECTED] added the comment: I wish I had realized this work was done or else I would have pushed to get this in for 2.6/3.0. Damn. Setting for 2.7/3.1, although if the decision was made it was easier to only have it in 3.1 that would be fine by me. Regardless, setting this to high since while it is not a bug fix, being able to make Tk apps that aren't quite so ugly would be REALLY nice and might re-invigorate use of tkinter. -- nosy: +brett.cannon priority: - high versions: +Python 2.7, Python 3.1 -Python 2.5, Python 2.6, Python 3.0 ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue2983 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3526] Customized malloc implementation on SunOS and AIX
Martin v. Löwis [EMAIL PROTECTED] added the comment: I cannot quite see why the problem is serious: even though the memory is not returned to the system, it will be swapped out to the swap file, so it doesn't consume any real memory (just swap space). I don't think Python should integrate a separate malloc implementation. Instead, Python's own memory allocate (obmalloc) should be changed to directly use the virtual memory interfaces of the operating system (i.e. mmap), bypassing the malloc of the C library. So I'm -1 on this patch. -- nosy: +loewis ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3526 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3436] csv.DictReader inconsistency
Skip Montanaro [EMAIL PROTECTED] added the comment: Committed as revision 65605. -- assignee: - skip.montanaro status: open - closed ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3436 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3529] Remove long integer literals from Python 3.0 tutorial
New submission from Jim Sizelove [EMAIL PROTECTED]: The distinction between integers and long integers has been removed in Python 3.0. The attached patch file changes the long literals to Python 3.0 integer literals in the Floating Point Arithmetic section of the tutorial. -- assignee: georg.brandl components: Documentation files: floatingpoint.diff keywords: patch messages: 70922 nosy: georg.brandl, jsizelove severity: normal status: open title: Remove long integer literals from Python 3.0 tutorial versions: Python 3.0 Added file: http://bugs.python.org/file11090/floatingpoint.diff ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3529 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3530] ast.NodeTransformer bug
New submission from daishi [EMAIL PROTECTED]:
I am testing python 2.6 from SVN version: 40110
I tried the following, based on the documentation
and example in the ast module. I would expect the
second 'compile' to succeed also, instead of
throwing an exception.
Python 2.6b2+ (unknown, Aug 6 2008, 18:05:08)
[GCC 4.2.3 (Ubuntu 4.2.3-2ubuntu7)] on linux2
Type help, copyright, credits or license for more information.
import ast
a = ast.parse('foo', mode='eval')
x = compile(a, 'unknown', mode='eval')
class RewriteName(ast.NodeTransformer):
... def visit_Name(self, node):
... return ast.copy_location(ast.Subscript(
... value=ast.Name(id='data', ctx=ast.Load()),
... slice=ast.Index(value=ast.Str(s=node.id)),
... ctx=node.ctx
... ), node)
...
a2 = RewriteName().visit(a)
x2 = compile(a2, 'unknown', mode='eval')
Traceback (most recent call last):
File stdin, line 1, in module
TypeError: required field lineno missing from expr
--
components: Library (Lib)
messages: 70923
nosy: daishiharada
severity: normal
status: open
title: ast.NodeTransformer bug
versions: Python 2.6
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3530
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3531] file read preallocs 'size' bytes which can cause memory problems
New submission from Andrew Dalke [EMAIL PROTECTED]: I wrote a buggy PNG parser which ended up doing several file.read(large value). It causes a MemoryError, which was strange because the file was only a few KB long. I tracked it down to the implementation of read(). When given a size hint it preallocates the return string with that size. If the hint is for 10MB then the string returned will be preallocated fro 10MB, even if the actual read is empty. Here's a reproducible BLOCKSIZE = 10*1024*1024 f=open(empty.txt, w) f.close() f=open(empty.txt) data = [] for i in range(1): s = f.read(BLOCKSIZE) assert len(s) == 0 data.append(s) I wasn't sure if this is properly a bug, but since the MemoryError exception I got was quite unexpected and required digging into the source code to figure out, I'll say that it is. -- components: Interpreter Core messages: 70924 nosy: dalke severity: normal status: open title: file read preallocs 'size' bytes which can cause memory problems type: resource usage ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3531 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
