date:20100126

[issue7766] sys.getwindowsversion as PyStructSequence

2010-01-26 Thread Eric Smith


Eric Smith e...@trueblade.com added the comment:

The more I think about this, the more concerned I am about changing the number 
of elements in the tuple. That's the change that broke platform.py. Maybe we 
should add a parameter named something like level, defaulting to 0.

0 = existing behavior, but with named tuple
1 = return named 9-tuple OSVERSIONINFOEX values
other values: reserved for future use

Or maybe we should make it a bool instead, and not worry about future expansion.

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7766
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue7782] new test for test_iter.py

2010-01-26 Thread showell


New submission from showell showel...@yahoo.com:

I would like to submit the following test to be part of the test_iter.py test 
suite:

def test_extends(self):
# This test would break on an incomplete patch to listobject.c
def gen():
for i in range(500):
yield i
lst = [0] * 500
for i in range(240):
lst.pop(0)
lst.extend(gen())

The history behind it is that I made a patch to listobject.c that obviously 
broke listextend(), but the tests did not catch it.  This was my failing test 
to improve my patch.  Regardless of what happens to the patch, I think it's a 
good idea to hammer on listextend() when it accepts an iterator, as it's a 
fairly tricky problem to extend a list when you do not know in advance how long 
it will be until the iterator gets exhausted.

--
components: Tests
messages: 98320
nosy: Steve Howell
severity: normal
status: open
title: new test for test_iter.py
type: behavior
versions: Python 3.2

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7782
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue5689] please support lzma compression as an extension and in the tarfile module

2010-01-26 Thread Glenn Linderman


Changes by Glenn Linderman v+pyt...@g.nevcal.com:


--
nosy: +v+python

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5689
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue7783] test_normalization fails when NormalizationTest.txt is outdated

2010-01-26 Thread Florent Xicluna


New submission from Florent Xicluna la...@yahoo.fr:

The test test_normalization download a file from the unicode.org website 
and keep it in the local cache Lib/test/data/ directory for next runs.
On test setup, it verifies if the 1st line contains the right version 
unicodedata.unidata_version.
It should unlink the file if it is outdated.
But it does not work as expected: it looks for the file in the wrong directory.

~ $ echo # NormalizationTest-3.0.0.txt ~ outdated version  
Lib/test/data/NormalizationTest.txt

~ $ ./python -m test.regrtest -uall test_normalization
test_normalization
test test_normalization failed -- Traceback (most recent call last):
  File ./Lib/test/test_normalization.py, line 96, in test_main
self.assertTrue(X == NFC(X) == NFD(X) == NFKC(X) == NFKD(X), c)
AssertionError: 160

1 test failed:
test_normalization

~ $ cat Lib/test/data/NormalizationTest.txt
# NormalizationTest-3.0.0.txt ~ outdated version

--
components: Tests, Unicode
messages: 98321
nosy: flox
severity: normal
status: open
title: test_normalization fails when NormalizationTest.txt is outdated
type: behavior
versions: Python 2.7

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7783
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue7783] test_normalization fails when NormalizationTest.txt is outdated

2010-01-26 Thread Florent Xicluna


Florent Xicluna la...@yahoo.fr added the comment:

Here is a patch.

The function test_support.open_urlresource is enhanced with an optional 
argument check which receives a function. This check function accepts an 
open file as input and return False if the file is outdated.

--
keywords: +patch
versions: +Python 3.2
Added file: http://bugs.python.org/file16007/issue7783_normalization.diff

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7783
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue7766] sys.getwindowsversion as PyStructSequence

2010-01-26 Thread Marc-Andre Lemburg


Marc-Andre Lemburg m...@egenix.com added the comment:

Eric Smith wrote:
 
 Eric Smith e...@trueblade.com added the comment:
 
 The more I think about this, the more concerned I am about changing the 
 number of elements in the tuple. That's the change that broke platform.py. 
 Maybe we should add a parameter named something like level, defaulting to 0.
 
 0 = existing behavior, but with named tuple
 1 = return named 9-tuple OSVERSIONINFOEX values
 other values: reserved for future use
 
 Or maybe we should make it a bool instead, and not worry about future 
 expansion.

The usual approach to such problems is keeping the number of tuple
items and their order the same and only add new items as additional
attributes to the struct.

See the CodecInfo tuple in codecs.py for an example on how this is
done. The tuple is still a 4-tuple, but it provides access to more
items via named attributes.

--
nosy: +lemburg

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7766
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue7784] patch for making list/insert at the top of the list avoid memmoves

2010-01-26 Thread showell


New submission from showell showel...@yahoo.com:

I am attaching a patch to improve the performance of list operations that 
insert or delete elements at the front of the list.  The patch has had some 
discussion on python-dev in the thread entitled patch to make list.pop(0) work 
in O(1) time.

So far the verdict is not to touch list internals to achieve this performance 
gain, but I am looking to improve the patch regardless and possibly include it 
in a PEP that documents the decision not to incorporate the patch, with the 
hope that it either prevents future duplication of effort or eventually gets 
accepted.

At a bare minimum, the patch needs extensive code review, as it touches a lot 
of internals, and it needs stylistic cleanup.  But it does pass all the tests, 
and it has been benchmarked to show 100X speed improvement on a small test case.

--
components: Interpreter Core
files: DIFF
messages: 98324
nosy: Steve Howell
severity: normal
status: open
title: patch for making list/insert at the top of the list avoid memmoves
type: performance
versions: Python 3.2
Added file: http://bugs.python.org/file16008/DIFF

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7784
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue1205239] Let shift operators take any integer value

2010-01-26 Thread Mark Dickinson


Mark Dickinson dicki...@gmail.com added the comment:

Interesting.  I agree that that looks like a case where it would be desirable 
for a  -n to do a  n.

By the way, I don't think your formula is quite correct:  your crc is going to 
grow unboundedly as extra data bytes come in.  I suspect that you want to mask 
the result with (1  crc_width) - 1 after each update.
(And what's the ' 0xFF' for?  Isn't it redundant?)

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1205239
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue1205239] Let shift operators take any integer value

2010-01-26 Thread Mark Dickinson


Mark Dickinson dicki...@gmail.com added the comment:

One other thought: you could always compute the expression

  crc  (crc_width - 8)

as

  crc  8  crc_width

Since you're computing crc  8 anyway, this doesn't increase the operations 
count, so probably wouldn't significant impact performance.

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1205239
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue7615] unicode_escape codec does not escape quotes

2010-01-26 Thread Marc-Andre Lemburg

Marc-Andre Lemburg m...@egenix.com added the comment:

Amaury Forgeot d'Arc wrote:
I feel uneasy to change the default unicode-escape encoding.
I think that we mix two features here; to transfer a unicode string between
two points, programs must agree on where the data ends, and how characters
are represented as bytes.
All codecs including unicode-escape only dealt with byte conversion;
(unicode-escape converts everything to printable 7bit ascii);
these patches want to add a feature related to the where does the string
end issue, and is only aimed at python code containers. Other transports
and protocols may choose different delimiters.

My point is that unicode-escape used to not change printable 7-bit ascii
characters, and the patches will change this.

And actually this will break existing code. It did not take me long to find
two examples of programs which embed unicode_escape-encoded text between
quotes, and take care themselves of escaping quotes. First example generates
javascript code, the second generates SQL statements:
http://github.com/chriseppstein/pywebmvc/blob/master/src/code/pywebmvc/tools/searchtool.py#L450
http://gitweb.sabayon.org/?p=entropy.git;a=blob;f=libraries/entropy/db/__init__.py;h=2d818455efa347f35b2e96d787fefd338055d066;hb=HEAD#l6463

Ouch... these codecs should not have been used outside
Python. I wonder why these applications don't use repr(text)
to format the JavaScript/SQL strings.

I guess this is the result of documenting them in
http://docs.python.org/library/codecs.html#standard-encodings

Too bad that the docs actually say Produce a string that is
suitable as Unicode literal in Python source code. The codecs
main intent was to *decode* Unicode literals in Python source
code to Unicode objects...

The naming in the examples you mention also suggest that the
programmers used the table from the docs - they use
unicode_escape as codec name, not the standard
unicode-escape name which we use throughout the Python
code.

The fact that the demonstrated actual use already does apply the
extra quote escaping suggests that we cannot easily add this
to the existing codecs. It would break those applications, since
they'd be applying double-escaping.

This does not prevent the creation of a new codec, let's call it
'python-unicode-escape' [ or 'repr' :-) ]

I think that's a good idea to move forward.

Python 3.x comes with a new Unicode repr() format which we could
turn into a new codec: it automatically adds the quotes, processes
the in-string quotes and backslashes and also escapes \t, \n and \r
as well as all non-printable code points.

As for naming the new codec, I'd suggest unicode-repr since
that's what it implements.

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7615
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

1 2 >

1 - 100 of 108 matches

Mail list logo