[issue5336] collections.namedtuple generates code causing PyChecker warnings

2009-02-21 Thread Mikhail Bessonov

New submission from Mikhail Bessonov za...@mail.ru:

The first argument of some methods generated by collections.namedtuple 
differs from 'self'. It upsets a number of code checkers, notably 
PyChecker, because in most cases it is indeed an error. As a result, 
the code using collections.namedtuple does not pass PyChecker, which is 
a commit or release requirement in many projects.

The solution would be to rename the first argument of each method to 
'self'.

A sample 2-line program demonstrating the error is provided below.

import collections
DocRecord = collections.namedtuple('DocRecord', 'id, date, name, desc',
verbose = True)

Here's the PyChecker output. Methods that cause trouble are 'def _asdict
(t):', etc.

E:\src\mini-crawlerE:\Python26\python.exe E:\Python26\Lib\site-packages
\pychecker\checker.py test.py 
class DocRecord(tuple):
'DocRecord(id, date, name, desc)' 

__slots__ = () 

_fields = ('id', 'date', 'name', 'desc') 

def __new__(cls, id, date, name, desc):
return tuple.__new__(cls, (id, date, name, desc)) 

@classmethod
def _make(cls, iterable, new=tuple.__new__, len=len):
'Make a new DocRecord object from a sequence or iterable'
result = new(cls, iterable)
if len(result) != 4:
raise TypeError('Expected 4 arguments, got %d' % len
(result))
return result 

def __repr__(self):
return 'DocRecord(id=%r, date=%r, name=%r, desc=%r)' % self 

def _asdict(t):
'Return a new dict which maps field names to their values'
return {'id': t[0], 'date': t[1], 'name': t[2], 'desc': t
[3]} 

def _replace(self, **kwds):
'Return a new DocRecord object replacing specified fields 
with new values'
result = self._make(map(kwds.pop, ('id', 'date', 'name', 
'desc'), self))
if kwds:
raise ValueError('Got unexpected field names: %r' % 
kwds.keys())
return result 

def __getnewargs__(self):
return tuple(self) 

id = property(itemgetter(0))
date = property(itemgetter(1))
name = property(itemgetter(2))
desc = property(itemgetter(3))


Warnings...

string:22: self is not first method argument

--
components: Library (Lib)
messages: 82562
nosy: mbessonov
severity: normal
status: open
title: collections.namedtuple generates code causing PyChecker warnings
type: behavior
versions: Python 2.6

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



[issue4258] Use 30-bit digits instead of 15-bit digits for Python integers.

2009-02-21 Thread Mark Dickinson

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

Adding Tim Peters to the nosy list, mainly to give him an opportunity to 
throw up his hands in horror at my rewrite of his (I'm guessing) 
implementation of division.

--
nosy: +tim_one

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



[issue5163] tkinter.scrolledtext: new text is hidden after using insert()

2009-02-21 Thread Guilherme Polo

Guilherme Polo ggp...@gmail.com added the comment:

In this case I'm closing it.

--
resolution:  - rejected
status: open - closed

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



[issue5323] document expected/required behavior of 3.x io subsystem with respect to buffering

2009-02-21 Thread Antoine Pitrou

Antoine Pitrou pit...@free.fr added the comment:

RDM, all the classes you mentioned should indeed be able to do short
reads on pipes, sockets and the like. That's how they are tested in
test_io.py: against mock raw i/o classes which only return a few bytes
at a time (e.g. only 5 bytes will be filled in a 4096-byte buffer).

However, I encourage you once again to *experiment* with the 3.x i.o
library and share your results with us. This is the best way for us to
know whether common use cases are really covered.

(Amaury, as for the `telling` flag in TextIOWrapper, we should so some
performance measurements, and then suppress it if there's no difference)

--
nosy: +pitrou

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



[issue5336] collections.namedtuple generates code causing PyChecker warnings

2009-02-21 Thread Benjamin Peterson

Changes by Benjamin Peterson benja...@python.org:


--
assignee:  - rhettinger
nosy: +rhettinger

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



[issue5330] profile and cProfile do not report C functions called with keyword arguments

2009-02-21 Thread Hagen Fürstenau

Hagen Fürstenau hfuerste...@gmx.net added the comment:

I found the reason for this problem: C function calls with keyword
arguments follow a different path than those without keywords in the
function call_function of ceval.c. They end up being handled by
do_call, but there the call is not wrapped by C_TRACE, so a profiler
function registered through sys.setprofile() doesn't see such calls.

The same problem occurs in ext_do_call, which gets called in the
handling of the opcodes CALL_FUNCTION_VAR and CALL_FUNCTION_KW, causing
omission of a function call like

 [].sort(**{'reverse':True})

from the profiler report.

The attached patch solves the problem, but I don't know if it's the best
solution. Handling calls with keyword arguments at the beginning of
call_function seems to have bigger performance drawbacks though.

--
keywords: +patch
Added file: http://bugs.python.org/file13146/ceval.patch

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



[issue5329] os.popen2 and os.popen3 in python 2.6 incompatible with os.popen* in python 2.5

2009-02-21 Thread Antoine Pitrou

Antoine Pitrou pit...@free.fr added the comment:

Adding a couple of unit tests would be nice.

--
nosy: +pitrou
priority:  - high
versions: +Python 2.7

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



[issue5323] document expected/required behavior of 3.x io subsystem with respect to buffering

2009-02-21 Thread R. David Murray

R. David Murray rdmur...@bitdance.com added the comment:

On Sat, 21 Feb 2009 at 13:14, Antoine Pitrou wrote:
 Antoine Pitrou pit...@free.fr added the comment:

 RDM, all the classes you mentioned should indeed be able to do short
 reads on pipes, sockets and the like. That's how they are tested in
 test_io.py: against mock raw i/o classes which only return a few bytes
 at a time (e.g. only 5 bytes will be filled in a 4096-byte buffer).

My questions in the last comment were directed at trying to clarify
the documentation.

I think my most important point there is whether or not 'read1' should
be added to the BufferedIOBase ABI.  I believe it should be, since
if a class derived from BufferedIOBase does not implement it and is
passed to TextIOWrapper, it will fail.

 However, I encourage you once again to *experiment* with the 3.x i.o
 library and share your results with us. This is the best way for us to
 know whether common use cases are really covered.

As I said, I plan to do so.  I needed to understand the intent first,
though, and reading the docs resulted in some doc questions.  Should I
be opening each point in a separate issue and/or providing a suggested
doc patch?  I'm new to trying to help out via the tracker, so best
practice pointers are welcome.

--RDM

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



[issue5337] Scanner class in re module undocumented

2009-02-21 Thread Michael Foord

New submission from Michael Foord mich...@voidspace.org.uk:

There is a useful Scanner class in the re module which is undocumented.

See:

http://mail.python.org/pipermail/python-dev/2003-April/035075.html
http://www.evanfosmark.com/2009/02/sexy-lexing-with-python/

--
assignee: georg.brandl
components: Documentation
messages: 82569
nosy: georg.brandl, mfoord
severity: normal
status: open
title: Scanner class in re module undocumented
versions: Python 2.6, Python 3.0

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



[issue5308] cannot marshal objects with more than 2**31 elements

2009-02-21 Thread Mark Dickinson

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

It wouldn't hurt to add the overflow checks though, would it?

--
assignee:  - marketdickinson
priority:  - normal

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



[issue5338] Typo in Python/C API sect 1.2.1

2009-02-21 Thread Ruth Aydt

New submission from Ruth Aydt a...@hdfgroup.org:

In Section 1.2.1 of the 2.6.1 Python/C API documentation, I believe
there is a typo.

First sentence in second paragraph in Reference Count Details subsection.

... function passes it a reference... should be
... function passes in a reference...

--
assignee: georg.brandl
components: Documentation
messages: 82571
nosy: aydt, georg.brandl
severity: normal
status: open
title: Typo in Python/C API sect 1.2.1
versions: Python 2.6

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



[issue5339] Typo in Python/C API Chapter 2

2009-02-21 Thread Ruth Aydt

New submission from Ruth Aydt a...@hdfgroup.org:

Python/C API Documentation for 2.6.1
Chapter 2, 3rd paragraph.

On particular issue... should be One particular issue...

--
assignee: georg.brandl
components: Documentation
messages: 82572
nosy: aydt, georg.brandl
severity: normal
status: open
title: Typo in Python/C API Chapter 2
versions: Python 2.6

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



[issue5339] Typo in Python/C API Chapter 2

2009-02-21 Thread Georg Brandl

Georg Brandl ge...@python.org added the comment:

Thanks, fixed in r69840.

--
resolution:  - fixed
status: open - closed

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



[issue5338] Typo in Python/C API sect 1.2.1

2009-02-21 Thread Georg Brandl

Georg Brandl ge...@python.org added the comment:

Thanks, fixed in r69840.

--
resolution:  - fixed
status: open - closed

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



[issue5340] Change in cgi behavior breaks existing software

2009-02-21 Thread Bob Kline

New submission from Bob Kline bkl...@rksystems.com:

We just upgraded Python to 2.6 on some of our servers and a number of
our CGI scripts broke because the cgi module has changed the way it
handles POST requests.  When the 'action' attribute was not present in
the form element on an HTML page the module behaved as if the value of
the attribute was the URL which brought the user to the page with the
form, but without the query (?x=y...) part.  Now FieldStorage.getvalue()
is giving the script a list of two copies of the value for some of the
parameters (folding in the parameters from the previous request) instead
of the single string it used to return for each.  I searched the python
mailing list looking for a discussion of the proposal to impose this
change of behavior, and perhaps I wasn't using the right phrases in my
search, but I didn't find anything.  I didn't get many responses when I
asked for pointers to this discussion, but the few I did get were from
people who were as surprised as we were.  It's not clear to us (or to
those who responded on the mailing list) that the applicable RFCs
provide completely clear and unambiguous guidance as to which behavior
is correct, but even if the new behavior is correct, it is unusual to
have changes to the library which break existing code introduced without
any discussion of the impact, or transition period, or options to
preserve the previous behavior.  For what it's worth, it appears that
Perl and PHP (which probably account for the bulk of non-Python CGI
scripts in the wild) both behave the way the pre-2.6 cgi module did.  We
have a workaround (modify all our CGI scripts to explicitly set the
action attribute without the parameter suffix), but I was asked by one
of the regulars on the mailing list to file a bug report here, so I'm
complying with that request.

It appears that the breaking change was introduced with
http://svn.python.org/view?rev=64447view=rev in connection with
http://bugs.python.org/issue1817.

See
http://mail.python.org/pipermail/python-list/2009-February/529130.html
for repro instructions.

--
components: Library (Lib)
messages: 82575
nosy: bkline
severity: normal
status: open
title: Change in cgi behavior breaks existing software
type: behavior
versions: Python 2.6

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



[issue4565] Rewrite the IO stack in C

2009-02-21 Thread Antoine Pitrou

Antoine Pitrou pit...@free.fr added the comment:

The StringIO rewrite is finished now.

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



[issue5341] A selection of spelling errors and typos throughout source

2009-02-21 Thread Mark Dickinson

New submission from Mark Dickinson dicki...@gmail.com:

Here's a patch that represents the result of grepping through the source 
for some of my favo(u)rite spelling errors.

Georg, I reali(z/s)e that most of these fixes are outside the Doc/ 
directory, but are you interested in taking a look at these?  Please 
unassign if not.

Two notes:

- I'm pretty sure that all of these are genuine errors.  The only one
that may be controversial is 'builtin - built-in' (when used as an 
adjective).  The 'Apple Publications Style Guide' seems to use built-in in 
preference to builtin.  I also think I missed a few of these.

- My (American English) spell-checker complains about 'signalled', but it 
looks fine when I put my British English eyes in.  The docs contain  
instances of both 'signalled' *and* 'signaled'.  Is there any consensus on 
whether American English or British English should be used for Python's 
documentation?  (Should also check for 'signalling' versus 'signaling'.)

--
assignee: georg.brandl
components: Documentation
files: spellings.patch
keywords: patch
messages: 82577
nosy: georg.brandl, marketdickinson
priority: low
severity: normal
status: open
title: A selection of spelling errors and typos throughout source
versions: Python 2.6, Python 2.7, Python 3.0, Python 3.1
Added file: http://bugs.python.org/file13147/spellings.patch

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



[issue5341] A selection of spelling errors and typos throughout source

2009-02-21 Thread Georg Brandl

Georg Brandl ge...@python.org added the comment:

I reviewed the patch and found nothing wrong. (BTW, if you noticed the
almost-total lack of its-it's errors, it's because I fixed all of them
some time ago :)

built-in is fine.

About AE/BE: I think we had a consensus somewhere that we have no fixed
variant, but if you write a larger chunk of text you may write in your
preferred spelling.  I guess that if you look for instances of -or vs
-our you might find lots of stuff too.  So I'd leave them alone.

--
assignee: georg.brandl - marketdickinson
resolution:  - accepted

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



[issue5313] multiprocessing.process using os.close(sys.stdin.fileno) instead of sys.stdin.close()

2009-02-21 Thread Jesse Noller

Jesse Noller jnol...@gmail.com added the comment:

Joshua Judson Rosen to python-list


Jesse Noller jnol...@gmail.com writes:

 On Tue, Feb 17, 2009 at 10:34 PM, Graham Dumpleton
 graham.dumple...@gmail.com wrote:
  Why is the multiprocessing module, ie., multiprocessing/process.py, in
  _bootstrap() doing:
 
   os.close(sys.stdin.fileno())
 
  rather than:
 
   sys.stdin.close()
 
  Technically it is feasible that stdin could have been replaced with
  something other than a file object, where the replacement doesn't have
  a fileno() method.
 
  In that sort of situation an AttributeError would be raised, which
  isn't going to be caught as either OSError or ValueError, which is all
  the code watches out for.

 I don't know why it was implemented that way. File an issue on the
 tracker and assign it to me (jnoller) please.

My guess would be: because it's also possible for sys.stdin to be a
file that's open in read+*write* mode, and for that file to have
pending output buffered (for example, in the case of a socketfile).

There's a general guideline, inherited from C, that one should ensure
that the higher-level close() routine is invoked on a given
file-descriptor in at most *one* process after that descriptor has
passed through a fork(); in the other (probably child) processes, the
lower-level close() routine should be called to avoid a
double-flush--whereby buffered data is flushed out of one process, and
then the *same* buffered data is flushed out of the (other)
child-/parent-process' copy of the file-object.

So, if you call sys.stdin.close() in the child-process in
_bootstrap(), then it could lead to a double-flush corrupting output
somewhere in the application that uses the multiprocessing module.

You can expect similar issues with just about /any/ `file-like objects'
that might have `file-like semantics' of buffering data and flushing
it on close, also--because you end up with multiple copies of the same
object in `pre-flush' state, and each copy tries to flush at some point.

As such, I'd recommend against just using .close(); you might use
something like `if hasattr(sys.stdin, fileno): ...'; but, if your
`else' clause unconditionally calls sys.stdin.close(), then you still
have double-flush problems if someone's set sys.stdin to a file-like
object with output-buffering.

I guess you could try calling that an `edge-case' and seeing if anyone
screams. It'd be sort-of nice if there was finer granularity in the
file API--maybe if file.close() took a boolean `flush' argument

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



[issue4565] Rewrite the IO stack in C

2009-02-21 Thread Benjamin Peterson

Benjamin Peterson benja...@python.org added the comment:

Ok. I've split the Python io implementation into the _pyio module and
rewritten the tests. All the C ones are passing, but some Python
implementation ones are failing.

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



[issue5336] collections.namedtuple generates code causing PyChecker warnings

2009-02-21 Thread Raymond Hettinger

Raymond Hettinger rhettin...@users.sourceforge.net added the comment:

Will look at this one.  Am initially disinclined to change _asdict()
because I like its compact presentation.

--
priority:  - low

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



[issue1282] re module needs to support bytes / memoryview well

2009-02-21 Thread Benjamin Peterson

Benjamin Peterson benja...@python.org added the comment:

re has supported bytes for a while now.

--
nosy: +benjamin.peterson
resolution: accepted - out of date
status: open - closed

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



[issue5308] cannot marshal objects with more than 2**31 elements

2009-02-21 Thread Raymond Hettinger

Raymond Hettinger rhettin...@users.sourceforge.net added the comment:

Why not.  Besides it ought to be fun to write the test case for this one :-)

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



[issue5341] A selection of spelling errors and typos throughout source

2009-02-21 Thread Raymond Hettinger

Raymond Hettinger rhettin...@users.sourceforge.net added the comment:

Please do not change builtin to built-in.  In a python context, it reads
fine as one word.

--
nosy: +rhettinger

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



[issue2396] Backport memoryview object to Python 2.7

2009-02-21 Thread Benjamin Peterson

Benjamin Peterson benja...@python.org added the comment:

Some comments:

- PyBytes_* API is fine.
- memory_str should die.
- Py_TPFLAGS_HAVE_NEWBUFFER needs to be documented.

Otherwise it looks good.

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



[issue5342] distutils removing old files, deleting unneeded old files from installed location.

2009-02-21 Thread Rene Dudfield

New submission from Rene Dudfield ill...@users.sourceforge.net:

A common problem is removing old files from the installed location.

eg.
version 1 installs.
site-packages/packagename/bla.so

version 2 installs.
site-packages/packagename/_bla.so
site-packages/packagename/bla.py


However, in version 2 if we install over the top of version 1, distutils
does not remove bla.so.  Which causes the package to break because
bla.so will be used instead of bla.py
 

distutils should be able to be given a list of old files to make sure
are removed from the package.

It should work with the various installers... msi, dmg etc, as well as
when using setup.py install.

I've seen this cause breakage with numerous packages.  The solution is
to hack some old file detection into each package, or tell users 'delete
the old install first'.  Neither of which is really nice.

Specifying an old_files meta data should be able to help.

--
assignee: tarek
components: Distutils
messages: 82586
nosy: illume, tarek
severity: normal
status: open
title: distutils removing old files, deleting unneeded old files from installed 
location.
type: feature request

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



[issue4524] Build fails at running build_scripts

2009-02-21 Thread Tarek Ziadé

Tarek Ziadé ziade.ta...@gmail.com added the comment:

fixed in r69598. Thanks for the patch Amaury.

--
status: open - closed

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



[issue5342] distutils removing old files, deleting unneeded old files from installed location.

2009-02-21 Thread Tarek Ziadé

Tarek Ziadé ziade.ta...@gmail.com added the comment:

A uninstall command, based on the record of installed files, will be
proposed for #4673.

It should adress your problem, since we will be able to add a new option
in the install command.

I am leaving this issue open so we can keep track of this need.

--
versions: +Python 2.7, Python 3.1

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



[issue1578269] Add os.link() and os.symlink() support for Windows

2009-02-21 Thread Antoine Pitrou

Changes by Antoine Pitrou pit...@free.fr:


--
versions: +Python 2.7, Python 3.1 -Python 2.6

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



[issue5340] Change in cgi behavior breaks existing software

2009-02-21 Thread Paul Boddie

Paul Boddie p...@boddie.org.uk added the comment:

The issue of distinguishing between query-originating parameters and
form-originating parameters has been around for a very long time, and
in my own work, especially where the cgi module has been used, I've
been careful to distinguish between the two types and to merge them
only if this is desired.

See these messages for historical context around this issue:

http://mail.python.org/pipermail/web-sig/2003-October/60.html
http://mail.python.org/pipermail/web-sig/2003-October/000224.html
http://mail.python.org/pipermail/web-sig/2003-November/000257.html

Here's an old reference to the code which was changed in the cgi module:

http://mail.python.org/pipermail/web-sig/2003-November/000322.html

To summarise, a previous patch for this issue was never submitted
because of the risk of breaking existing code.

--
nosy: +pboddie

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



[issue4565] Rewrite the IO stack in C

2009-02-21 Thread Benjamin Peterson

Benjamin Peterson benja...@python.org added the comment:

Ok. I've fixed all the tests except
PyBufferedRandomTest.testFlushAndPeek and the garbage collections ones.

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



[issue5343] remove or make work pdb retval and rv

2009-02-21 Thread rocky bernstein

New submission from rocky bernstein ro...@gnu.org:

Remove pdb's undocumentedretval/rv debugger commands. 

It is conceivable this may have once worked on a version of Python long
ago, but not in recent releases. If it's of interest to make this work,
one approach would be to use the arg parameter passed into
trace_dispatch when the event type is return.

--
components: Library (Lib)
messages: 82591
nosy: rocky
severity: normal
status: open
title: remove or make work pdb retval and rv
type: behavior
versions: Python 2.6, Python 2.7

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



[issue1533164] Installed but not listed *.pyo break bdist_rpm

2009-02-21 Thread Tarek Ziadé

Tarek Ziadé ziade.ta...@gmail.com added the comment:

Mads,

I am all set now, under a fresh Fedora 10. But it seems that the
generated command for rpm does not work.

it calls:

$ rpm -ba --define _topdir xxx --clean build/xxx/foo.spec

-ba unkown option.

(My Fedora runs rpm 4.6.0rc3)

Anything special to set under Fedora ?

This is strange because bdist_rpm will call -ba, -bs or -bb and
none of them seem to be present in this version of RPM,
while it is present on the standalone RPM I run under MacOsX (5.0)

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



[issue5344] typo in what's new in 2.6

2009-02-21 Thread George Yoshida

New submission from George Yoshida qui...@users.sourceforge.net:

In What's new in 2.6  PEP 343 section, the following sentence lacks a
closing parenthesis:
 The expression is evaluated, and it should result in an object that
supports the context management protocol (that is, has __enter__() and
__exit__() methods.
http://docs.python.org/whatsnew/2.6.html#pep-343-the-with-statement

Patch attached

--
assignee: georg.brandl
components: Documentation
files: whatsnew.diff
keywords: patch, patch
messages: 82593
nosy: georg.brandl, quiver
priority: low
severity: normal
status: open
title: typo in what's new in 2.6
versions: Python 2.6
Added file: http://bugs.python.org/file13148/whatsnew.diff

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



[issue5328] Crash when doing some list iteration

2009-02-21 Thread qwjqwj

qwjqwj q...@papayamobile.com added the comment:

I used the script from issue 4732 and can reproduce segfault on my RHEL
5. After that I updated the system with yum update and get a new
version of libc. Currently the script cannot cause segfault after
updating. Thank you for your help.

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



[issue5345] cStringIO class name typo

2009-02-21 Thread qwjqwj

New submission from qwjqwj q...@papayamobile.com:

It has a typo error in cStringIO.StringIO's class name StringO:

 import cStringIO
 a=cStringIO.StringIO()
 a
cStringIO.StringO object at 0xb7eef240
 a.__class__.__name__
'StringO'

So we can't unpickle the object correctly with Python 2.5.4:

 import pickle
 pickle.loads(pickle.dumps(a))
Traceback (most recent call last):
  File stdin, line 1, in module
  File /usr/local/lib/python2.5/pickle.py, line 1366, in dumps
Pickler(file, protocol).dump(obj)
  File /usr/local/lib/python2.5/pickle.py, line 224, in dump
self.save(obj)
  File /usr/local/lib/python2.5/pickle.py, line 306, in save
rv = reduce(self.proto)
  File /usr/local/lib/python2.5/copy_reg.py, line 69, in _reduce_ex
raise TypeError, can't pickle %s objects % base.__name__
TypeError: can't pickle StringO objects


When using multiprocess library, it also use the pickling and unpickling
of cStringIO.StringIO object

--
components: Library (Lib)
messages: 82595
nosy: qwjqwj
severity: normal
status: open
title: cStringIO class name typo
versions: Python 2.5

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



[issue5345] cStringIO class name typo

2009-02-21 Thread qwjqwj

qwjqwj q...@papayamobile.com added the comment:

This bug also exists in Python 2.6.1

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