[issue648658] xmlrpc can't do proxied HTTP

[Geoffrey Bache]

Geoffrey Bache <[EMAIL PROTECTED]> added the comment:

Well, strictly speaking, yes. It just feels like a rather major omission
(when Python can do xmlrpc and handle proxies you hope it will handle
the combination).

"Desperate" doesn't really have a timeline, strangely enough :) I know I
will be talking to bazaar and bugzilla behind a proxy in the mid-term
future and it would be very useful to use an officially sanctioned
solution (though of course I will try the attached file if there isn't
one at the time).

I see Python 2.6 is nearing release candidates : is this likely to be
included or will we have to wait for 2.7 now?

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3646] MacOS X framework install to non-standard directory fails

[Konrad Hinsen]

New submission from Konrad Hinsen <[EMAIL PROTECTED]>:

The file Mac/README in Python 2.6b3 says:

Installing in another place, for instance $HOME/Library/Frameworks if 
you have no admin privileges on your machine, has only been tested very 
lightly. This can be done by configuring with --enable-
framework=$HOME/Library/Frameworks. The other two directories, 
"/Applications/MacPython-2.6" and /usr/local/bin, will then also be 
deposited in $HOME. This is sub-optimal for the unix tools, which you 
would want in $HOME/bin, but there is no easy way to fix this right
now.


In reality, the framework is installed in the directory given on the 
command line, but the installer then wants to write the app to 
/Applications/MacPython-2.6 and crashes due to lack of write permission:

DYLD_FRAMEWORK_PATH=/shared_scratch/Python-2.6b3:  ../python.exe 
./scripts/Buil\
dApplet.py \
--destroot "" \
--
python=/shared_scratch/Library/Frameworks/Python.framework/Versions/2\
.6/Resources/Python.app/Contents/MacOS/Python`test -f 
"/shared_scratch/Library/\
Frameworks/Python.framework/Versions/2.6/Resources/Python.app/Contents/M
acOS/Py\
thon-32" && echo "-32"`  \
--output "/Applications/Python 2.6/Build Applet.app" \
./scripts/BuildApplet.py
kCGErrorRangeCheck : Window Server communications from outside of 
session allow\
ed for root and console user only
./scripts/BuildApplet.py:34: DeprecationWarning: catching of string 
exceptions \
is deprecated
  except buildtools.BuildError, detail:
Traceback (most recent call last):
  File "./scripts/BuildApplet.py", line 149, in 
main()
  File "./scripts/BuildApplet.py", line 33, in main
buildapplet()
  File "./scripts/BuildApplet.py", line 116, in buildapplet
progress=verbose, destroot=destroot)
  File "/Volumes/User data/Scratch/Python-2.6b3/Lib/plat-
mac/buildtools.py", li\
ne 115, in process
copy_codefragment, raw, others, filename, destroot)
  File "/Volumes/User data/Scratch/Python-2.6b3/Lib/plat-
mac/buildtools.py", li\
ne 140, in process_common
is_update, raw, others, filename, destroot)
  File "/Volumes/User data/Scratch/Python-2.6b3/Lib/plat-
mac/buildtools.py", li\
ne 327, in process_common_macho
builder.build()
  File "/Volumes/User data/Scratch/Python-2.6b3/Lib/plat-
mac/bundlebuilder.py",\
 line 147, in build
os.mkdir(builddir)
OSError: [Errno 13] Permission denied: '/Applications/Python 2.6'
make[1]: *** [install_BuildApplet] Error 1
make: *** [frameworkinstallapps] Error 2

--
components: Build
messages: 71728
nosy: khinsen
severity: normal
status: open
title: MacOS X framework install to non-standard directory fails
versions: Python 2.6

___
Python tracker <[EMAIL PROTECTED]>

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

[issue1342811] Tkinter.Menu.delete doesn't delete command of entry

[Robert Schuppenies]

Robert Schuppenies <[EMAIL PROTECTED]> added the comment:

Fixed in r65971. Backported to the release25-maint and merged into the
py3k branch.

--
resolution:  -> fixed
status: open -> closed

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3643] Add more checks to testcapi

[STINNER Victor]

STINNER Victor <[EMAIL PROTECTED]> added the comment:

@benjamin.peterson: I know but the module (installed in CPython 
default installation) is for testing purpose only, but invalid uses of 
its method would lead to inconsistent CPython internal state and 
that's bad :-) If you tried to say that such issue is not critical: 
yes, it's just a suggestion to improve CPython ;-)

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3107] test_list uses unreasonable amounts of memory on 64-bit Linux

[Antoine Pitrou]

Antoine Pitrou <[EMAIL PROTECTED]> added the comment:

Thanks, Tony!

--
resolution:  -> fixed
status: open -> closed

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3338] cPickle segfault with deep recursion

[Antoine Pitrou]

Antoine Pitrou <[EMAIL PROTECTED]> added the comment:

> Well, it's definitely a bug, or inconsistency, if you like, between
> cPickle and pickle.

There is clearly a problem with cPickle stack consumption and a new bug has been
opened for this in #3640.

What I don't agree with is your argument that pickle and cPickle should have the
same recursion limits - it's just "foolish consistency" to ask for identical
behaviour on such a low-level and implementation-dependent issue.

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3625] test issues on 64bit windows

[Antoine Pitrou]

Antoine Pitrou <[EMAIL PROTECTED]> added the comment:

Mark, your patch is ok to me. You can check it in.

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3643] Add more checks to testcapi

[Antoine Pitrou]

Antoine Pitrou <[EMAIL PROTECTED]> added the comment:

Unless someone thinks it's somehow release-critical, I'm retargetting
this to 2.7/3.1.

--
nosy: +pitrou
versions: +Python 2.7, Python 3.1 -Python 2.6, Python 3.0

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3645] readline module Crashs on OpenBSD/amd64

[Antoine Pitrou]

Changes by Antoine Pitrou <[EMAIL PROTECTED]>:


--
keywords: +needs review, patch
priority:  -> release blocker
versions: +Python 2.6, Python 3.0

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3640] test_cpickle crash on AMD64 Windows build

[Antoine Pitrou]

Antoine Pitrou <[EMAIL PROTECTED]> added the comment:

In my opinion this is a bug in cPickle. It is completely wrong to
consume more than 3KB of stack space for each recursion level, and it
should be fixed.

--
components: +Library (Lib)
priority:  -> release blocker

___
Python tracker <[EMAIL PROTECTED]>

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

[issue2394] [Py3k] Finish the memoryview object implementation

[Antoine Pitrou]

Antoine Pitrou <[EMAIL PROTECTED]> added the comment:

Guido, do we retarget the rest of this to 3.1? It sounds more reasonable
to me.

--
nosy: +gvanrossum

___
Python tracker <[EMAIL PROTECTED]>

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

[issue2619] Document PEP 3118

[Antoine Pitrou]

Antoine Pitrou <[EMAIL PROTECTED]> added the comment:

Should this be a release blocker?

--
type: feature request -> behavior

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3101] global function _add_one_to_C

[Antoine Pitrou]

Changes by Antoine Pitrou <[EMAIL PROTECTED]>:


--
nosy: +pitrou

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3101] global function _add_one_to_C

[Antoine Pitrou]

Antoine Pitrou <[EMAIL PROTECTED]> added the comment:

A sensible solution would be to put all the memoryview / buffer API
stuff in the same standalone file (e.g. memoryobject.c), rather than
having half of it dumped in abstract.c.

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3611] invalid exception context

[Amaury Forgeot d'Arc]

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment:

Victor, your patch addresses the symptom of the problem, not the cause.

The cause is that in some cases, the exception context chain is lost. Of
course what could be a minor annoyance becomes dramatic when this
precisely happens in code that makes use of this context.

IMO, PyErr_SetObject should not restore the previous exc_* members; it's
not its job to correct others' mistakes.
I join a patch that only protects it from crashing in this case: it just
saves exc_value in a local variable.

The bug shown by lostcontext2.py is still unresolved, but at least it
won't crash the interpreter.

Added file: http://bugs.python.org/file11207/pyerr_seterror_protect.py

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3611] invalid exception context

[Antoine Pitrou]

Antoine Pitrou <[EMAIL PROTECTED]> added the comment:

Agreed with Amaury, it's not PyErr_SetObject's job to try to
save/restore the tstate->exc_* variables. We'll probably have to live
with the small context-losing glitches in 3.0.

For 3.1, a radical solution would be to drop the "exception
normalization" misfeature (which is a source of complications and
potential bugs) and always instantiate exception objects as soon as they
are raised rather than lazily. We need to make sure the performance loss
is reasonable though.

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3611] invalid exception context

[Antoine Pitrou]

Antoine Pitrou <[EMAIL PROTECTED]> added the comment:

Hmm, answering to myself, I don't think dropping exception normalization
would solve the problem, it would just let it occur in a different place...

___
Python tracker <[EMAIL PROTECTED]>

___
___
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

[mounty]

mounty <[EMAIL PROTECTED]> added the comment:

@ Terry J. Reedy

If it is working for you it doesn't necessarily mean that it is working
for mankind in general.

I traced down the problem to the OS X- implementation of Idle in general
and submitted an inquiry to the general python list as you suggested.
The feedback was null- nada- niente. But in the meantime I received a
nice bunch of Spam instead.

http://mail.python.org/pipermail/python-list/2008-August/504330.html

I believe the original poster has a French keyboard and seems to have 
similar problems. The problem is that Idle seems to ignore the
international local keyboard setting. And as we do have two significant
letters ("#" and "'") at the keyboard position where you have the "\"
Idle seems to filter the entry of a backslash.

@ marc 67
HTH

Cheers
Ulf

--
nosy: +mounty

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3647] urlparse - relative url parsing and joins to be RFC3986 compliance

[Senthil]

New submission from Senthil <[EMAIL PROTECTED]>:

Attaching two patches to make the current urlparse library, especially 
the relative url parsing and urljoin  to be RFC3986 compliance.
I have included all the tests prescribed in RFC3986 and verified them 
to pass with the patches.

Our parsing functionality of netloc (to 
username,password,hostname,port) is same as what RFC3986 specifies. It 
uses the term 'authority' instead of 'netloc'. I did not feel the need 
for name change. If required, it can done.

--
components: Library (Lib)
files: urlparse_rfc3986-py26.diff
keywords: patch
messages: 71743
nosy: orsenthil
severity: normal
status: open
title: urlparse - relative url parsing and joins to be RFC3986 compliance
versions: Python 2.6, Python 3.0
Added file: http://bugs.python.org/file11208/urlparse_rfc3986-py26.diff

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3647] urlparse - relative url parsing and joins to be RFC3986 compliance

[Senthil]

Changes by Senthil <[EMAIL PROTECTED]>:


Added file: http://bugs.python.org/file11209/urlparse_rfc3986-py3k.diff

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3644] ``make htmlview`` for docs fails on OS X

[Benjamin Peterson]

Benjamin Peterson <[EMAIL PROTECTED]> added the comment:

This is probably actually a problem with the webbrowser module. Try
running "import webbrowser; webbrowser.open('build/html/index.html')" on
the plain Python shell.

--
components: +Library (Lib) -Documentation
nosy: +benjamin.peterson

___
Python tracker <[EMAIL PROTECTED]>

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

[issue2968] Test_imports takes a long time to run

[Benjamin Peterson]

Benjamin Peterson <[EMAIL PROTECTED]> added the comment:

This is no longer an issue.

--
nosy: +benjamin.peterson
resolution:  -> fixed
status: open -> closed

___
Python tracker <[EMAIL PROTECTED]>

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

[issue1504] Add 2to3 fixer for (un)bound methods

[Benjamin Peterson]

Benjamin Peterson <[EMAIL PROTECTED]> added the comment:

Must this still be open?

--
nosy: +benjamin.peterson

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3648] 'ascii' shoud be range(256) or just set another default encoding

[electronixtar]

New submission from electronixtar <[EMAIL PROTECTED]>:

One of the MOST common scene for Python developers on CJK/Widecharacter 
is this error:

'ascii' codec can't decode byte 0xe5 in position 0: ordinal not in range
(128)


Why cann't Python just define ascii to range(256), or alternatively, 
just use another default encoding that handles 0x00 to 0xff. Sometimes 
encoding problems in Python are driving me mad.

Currently I am using mbcs, but it's only available on Windows.

--
components: Interpreter Core
messages: 71747
nosy: electronixtar
severity: normal
status: open
title: 'ascii' shoud be range(256) or just set another default encoding
type: behavior
versions: Python 2.5

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3187] os.listdir can return byte strings

[STINNER Victor]

STINNER Victor <[EMAIL PROTECTED]> added the comment:

I implemented the "invalid filename" class feature:
 - by default, os.listdir() raise an error (UnicodeDecodeError) on 
invalid filename. The previous behaviour was to return bytes object 
instead of str.
 - if invalid_filename=True: create an InvalidFilename class instance

InvalidFilename is not a bytes string, it's not a str string, it's a 
new class. It has three attributes:
 - bytes: the real filename
 - charset: charset (type str)
 - str: fake filename (type str) used by __str__() method

My patch also fixes os.path.join() to accept InvalidFilename: if at 
last one argument is an InvalidFilename, use InvalidFilename.join() 
(class method).

os.listdir() and os.unlink() are patched to accept InvalidFilename. 
unlink always accept InvalidFilename whereas listdir() only produces 
InvalidFilename is os.listdir(path, invalid_filename=True) is used.

I added an optional argument "invalid_filename" to shutil.rmtree(), 
default value is *True*.

To sum up, visible changes:
 - os.listdir() raise an error on invalid filename instead of return a 
mixed list of str and bytes
 - shutil.rmtree() manipulate str and InvalidFilename instead of str 
and bytes

Added file: http://bugs.python.org/file11210/invalid_filename.patch

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3187] os.listdir can return byte strings

[Guido van Rossum]

Guido van Rossum <[EMAIL PROTECTED]> added the comment:

I'm not interested in the InvalidFilename class; it's an API
complification that might seem right for your situation but will hinder
most other people.  However I *am* interested in a patch that makes
os.unlink() (and as many other functions as you can think of) accept
bytes.  You'll have to think what encoding to use on Windows though,
since (AFAIK) the Windows filesystem APIs *do* use Unicode.

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3639] segfaults calling warnings.warn() with non-string message

[Daniel Diniz]

Daniel Diniz <[EMAIL PROTECTED]> added the comment:

Brett,
I don't think I know C (and CPython) enough to fix this. I was able to
get rid of this specific segfault with this:

-const char *text_char = _PyUnicode_AsString(text);
+const char *text_char =
_PyUnicode_AsString(PyObject_Str(text));

But I have no idea whether I should also incref/decref the PyObject_Str.

--
keywords: +patch
Added file: http://bugs.python.org/file11211/_warnings.c.diff

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3187] os.listdir can return byte strings

[STINNER Victor]

STINNER Victor <[EMAIL PROTECTED]> added the comment:

@gvanrossum: os.unlink() and os.lstat() already accept byte filenames 
(but open() doesn't).

Ok, here is very small patch for posixpath.join() to accept bytes 
strings. This patch is enough to fix my initial problem (#3616).

Added file: http://bugs.python.org/file11212/posix_path_bytes.patch

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3187] os.listdir can return byte strings

[STINNER Victor]

STINNER Victor <[EMAIL PROTECTED]> added the comment:

My last patch (posix_join_bytes.patch) is also enough to fix the 
initial reported problem: error in posixpath.join() called by 
os.walk(). I tried os.walk() on a directory with invalid filenames and 
invalid directory name and it works well.

So the last bug is open() which disallow opening a file with an 
invalid name. So here is another patch for that.

Added file: http://bugs.python.org/file11213/io_byte_filename.patch

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3648] 'ascii' shoud be range(256) or just set another default encoding

[Antoine Pitrou]

Antoine Pitrou <[EMAIL PROTECTED]> added the comment:

> Sometimes 
> encoding problems in Python are driving me mad.

The thing is, they are not "encoding problems in Python", they are
encoding problems in the outside world. Python cannot know magically
which encoding is used in third-party data, so you have to tell it
yourself what the encoding is.

The default is "ascii" because only ASCII chars (from 32 to 127) can be
interpreted properly in most situations without having any knowledge of
the encoding (barring obsolete stuff such as EBCDIC, that is).

The only solution is to know what encoding you are expecting and
decode/encode it yourself. Python can't decide it for you.

--
nosy: +pitrou
resolution:  -> invalid
status: open -> closed

___
Python tracker <[EMAIL PROTECTED]>

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

[issue1777458] glob doesn't return unicode with unicode parameter

[Antoine Pitrou]

Antoine Pitrou <[EMAIL PROTECTED]> added the comment:

Seems fixed on 2.6.

Python 2.6b3+ (trunk, Aug 22 2008, 11:27:51) [MSC v.1500 32 bit (Intel)]
on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> import glob
>>> glob.glob("*.py")
['iocrash.py', 'setup.py']
>>> glob.glob(u"*.py")
[u'iocrash.py', u'setup.py']
>>> glob.glob(u"./*.py")
[u'.\\iocrash.py', u'.\\setup.py']

--
nosy: +pitrou

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3649] IA5 Encoding should be in the default encodings

[Pascal Bach]

New submission from Pascal Bach <[EMAIL PROTECTED]>:

This encoding is used in the GSM standard it is a 7-bit encoding similar
to ASCII. 
The encoding definition is found in:
Short Message Service Centre EMI - UCP Interface 4.6 Specification (p. 79)
as well as in: 
[3GPP 23.038] 3GPP TS 23.038 Alphabets and language-specific information.

I think this encoding would be useful for other GSM specific use cases.

--
components: Unicode
files: ia5.py
messages: 71755
nosy: pascal.bach
severity: normal
status: open
title: IA5 Encoding should be in the default encodings
type: feature request
versions: Python 2.5
Added file: http://bugs.python.org/file11214/ia5.py

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3187] os.listdir can return byte strings

[STINNER Victor]

STINNER Victor <[EMAIL PROTECTED]> added the comment:

Patch glob.glob() to accept directory with invalid filename (invalid 
in the filesystem charset): just ignore bytes => str conversion error.

Added file: http://bugs.python.org/file11216/glob1_bytes.patch

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3640] test_cpickle crash on AMD64 Windows build

[Amaury Forgeot d'Arc]

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment:

The problem comes from this local variable in batch_list() and batch_dict:
PyObject *slice[BATCHSIZE];
and BATCHSIZE=1000...

--
nosy: +amaury.forgeotdarc

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3187] os.listdir can return byte strings

[STINNER Victor]

STINNER Victor <[EMAIL PROTECTED]> added the comment:

To continue in the "accept bytes filenames" way, a new patch for 
fnmatch.filter(). Use sys.getfilesystemencoding() to convert the 
bytes. The patch contains a new unit test.

Added file: http://bugs.python.org/file11215/fnmatch_bytes.patch

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3595] Windows base64 Decode

[Eric Smith]

Eric Smith <[EMAIL PROTECTED]> added the comment:

Please upload your script, or (preferably) some small test code.

I suspect the problem is related to line endings and binary versus text
files.

--
nosy: +eric.smith

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3640] test_cpickle crash on AMD64 Windows build

[Amaury Forgeot d'Arc]

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment:

Attached patch removes the big array, items are saved when they are
fetched from the container.
I preserved the the special case when there is only one item.

The patch does not merge cleanly into py3k, but the functions batch_list
and batch_dict look very similar and suffer the same problem.

--
keywords: +needs review, patch
Added file: http://bugs.python.org/file11217/cpickle.patch

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3555] Regression: nested exceptions crash (Cannot recover from stack overflow)

[Daniel Diniz]

Daniel Diniz <[EMAIL PROTECTED]> added the comment:

Antoine,
All the cases I could find would be more "test" than "use" cases. Given
that most ways to abort I find in 3.0 are related to "undetected error"s
in trunk, I'm almost convinced that 3.0 is right here :)

My last worry is that it'd be kinda easy to get Fatal errors from
sane-ish functions and deeply nested input:

class rec:
def __str__(self):
return str(self)

def overflower(x):
try:
return overflower(x)
except:
print (x)

list_rec = [1001]
for _ in range(12): list_rec = [[[
[list_rec]
]]]

str_rec = rec()

overflower(1) # OK
overflower(list_rec) # Aborts
overflower(str_rec) # Aborts


Thanks for the feedback!
Attached is a file that shows how trunk is doing something weird when it
works (besides the other reported issues that arise from that).

Added file: http://bugs.python.org/file11218/nester.py

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3644] ``make htmlview`` for docs fails on OS X

[Brett Cannon]

Brett Cannon <[EMAIL PROTECTED]> added the comment:

On Fri, Aug 22, 2008 at 6:12 AM, Benjamin Peterson
<[EMAIL PROTECTED]> wrote:
>
> Benjamin Peterson <[EMAIL PROTECTED]> added the comment:
>
> This is probably actually a problem with the webbrowser module. Try
> running "import webbrowser; webbrowser.open('build/html/index.html')" on
> the plain Python shell.
>

Yep, it is webbrowser thing.

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3639] segfaults calling warnings.warn() with non-string message

[Brett Cannon]

Brett Cannon <[EMAIL PROTECTED]> added the comment:

On Fri, Aug 22, 2008 at 8:03 AM, Daniel Diniz <[EMAIL PROTECTED]> wrote:
>
> Daniel Diniz <[EMAIL PROTECTED]> added the comment:
>
> Brett,
> I don't think I know C (and CPython) enough to fix this. I was able to
> get rid of this specific segfault with this:
>
> -const char *text_char = _PyUnicode_AsString(text);
> +const char *text_char =
> _PyUnicode_AsString(PyObject_Str(text));
>
> But I have no idea whether I should also incref/decref the PyObject_Str.
>

That's along the lines of what needs to be done (and what I was
planning on doing), although you need to do more error checking on the
return values. Plus the patch I am cooking up adds more checks in the
code for the return value of _PyUnicode_AsString().

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3640] test_cpickle crash on AMD64 Windows build

[Antoine Pitrou]

Antoine Pitrou <[EMAIL PROTECTED]> added the comment:

Here is an additional patch which adds a cpickle test to
Misc/find_recursion_limit.py. It helps show that Amaury's patch does fix
the issue. +1 for applying it.

Added file: http://bugs.python.org/file11219/find_recursion_limit.patch

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3639] segfaults calling warnings.warn() with non-string message

[Brett Cannon]

Brett Cannon <[EMAIL PROTECTED]> added the comment:

The patch doesn't actually bother with a translation as the code causing
issue is only there to prevent infinite recursion. So if the object
being used is not a string, then there is no need to worry as it is not
part of the infinite recursion problem.

I also added a bunch of missing error checks.

--
keywords: +needs review
Added file: http://bugs.python.org/file11220/fix_warn_funky_types.diff

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3639] segfaults calling warnings.warn() with non-string message

[Benjamin Peterson]

Benjamin Peterson <[EMAIL PROTECTED]> added the comment:

Brett, is this patch ready for review?

--
nosy: +benjamin.peterson

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3352] Deficiencies in multiprocessing/threading API

[Antoine Pitrou]

Antoine Pitrou <[EMAIL PROTECTED]> added the comment:

There are still some instances of get_name() in threading.py itself,
which gives errors like the following:


Unhandled exception in thread started by >
Traceback (most recent call last):
  File "/home/antoine/cpython/cpickle/Lib/threading.py", line 499, in
__bootstrap
self.__bootstrap_inner()
  File "/home/antoine/cpython/cpickle/Lib/threading.py", line 537, in
__bootstrap_inner
(self.get_name(), _format_exc()))
AttributeError: 'Thread' object has no attribute 'get_name'

--
nosy: +pitrou

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3352] Deficiencies in multiprocessing/threading API

[Benjamin Peterson]

Benjamin Peterson <[EMAIL PROTECTED]> added the comment:

Here's a patch.

Added file: http://bugs.python.org/file11221/get_name.patch

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3187] os.listdir can return byte strings

[Guido van Rossum]

Guido van Rossum <[EMAIL PROTECTED]> added the comment:

See http://codereview.appspot.com/3055 for a code review of Victor's
latest patches.

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3643] Add more checks to testcapi

[Benjamin Peterson]

Benjamin Peterson <[EMAIL PROTECTED]> added the comment:

Ok. I'll apply your patches when we get to 2.7. Do ping me if a forget,
though.

--
assignee:  -> benjamin.peterson

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3649] IA5 Encoding should be in the default encodings

[Amaury Forgeot d'Arc]

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment:

The provided file does not work for "EXTENSION" characters:

>>> import ia5
>>> u"[a]".encode("ia5")
Traceback (most recent call last):
  File "", line 1, in 
  File "ia5.py", line 18, in encode
return codecs.charmap_encode(input,errors,encoding_map)
TypeError: character mapping must be in range(256)

I doubt this can be achieved with just a charmap. You will have to roll
your own incremental stateful decoder.
Are you willing to do it?

--
nosy: +amaury.forgeotdarc

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3642] Objects/obmalloc.c:529: warning: comparison is always false due to limited range of data type

[Christian Heimes]

Christian Heimes <[EMAIL PROTECTED]> added the comment:

The warning in obmalloc.c was silenced in r65975 (trunk) and r65976 (py3k)

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3639] segfaults calling warnings.warn() with non-string message

[Brett Cannon]

Brett Cannon <[EMAIL PROTECTED]> added the comment:

That's why the keyword is set. =)

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3639] segfaults calling warnings.warn() with non-string message

[Benjamin Peterson]

Benjamin Peterson <[EMAIL PROTECTED]> added the comment:

On Fri, Aug 22, 2008 at 2:59 PM, Brett Cannon <[EMAIL PROTECTED]> wrote:
>
> Brett Cannon <[EMAIL PROTECTED]> added the comment:
>
> That's why the keyword is set. =)

Ah. I missed that. :) The patch looks fine.
>
> ___
> Python tracker <[EMAIL PROTECTED]>
> 
> ___
>

-- 
Cheers,
Benjamin Peterson
"There's no place like 127.0.0.1."

___
Python tracker <[EMAIL PROTECTED]>

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

[issue2367] Fixer to handle new places where parentheses are needed

[Benjamin Peterson]

Benjamin Peterson <[EMAIL PROTECTED]> added the comment:

Thanks for the work! I reviewed the code, added support for generator
expressions, and wrote a few more tests. Committed in r65981.

--
resolution:  -> fixed
status: open -> closed

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3649] IA5 Encoding should be in the default encodings

[Pascal Bach]

Pascal Bach <[EMAIL PROTECTED]> added the comment:

Well I have seen the problem. 

I'm willing to do this to improve python, but I don't know exactly how
to do it.

I looked at how utf-8 and utf-7 are done but I didn't exactly
understand, are they based on C code?

Is there an example how this needs to be done? It would be nice if you
could get me some help where to start.

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3563] fix_idioms.py generates bad code

[Terry J. Reedy]

Terry J. Reedy <[EMAIL PROTECTED]> added the comment:

Why is the statement, whatever it is, even being touched?
Would not the same problem arise with any following outdented line?

IOW, why not delete that pair of lines from fix_idioms.py?
Does that break anything else in test_fixers?

--
nosy: +tjreedy

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3602] Move test.test_suport.catch_warning() to the 'warnings' module

[Brett Cannon]

Brett Cannon <[EMAIL PROTECTED]> added the comment:

I think I can clean up the code by shifting WarningMessage over to a
subclass of namedtuple and moving WarningsRecorder over to a subclass of
list.

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3650] Memory leak in bytes.split()

[Amaury Forgeot d'Arc]

New submission from Amaury Forgeot d'Arc <[EMAIL PROTECTED]>:

./python Lib/test/regrtest.py -R:: test_bytes
reveals a leak in py3k.

This is exactly the same as the one corrected by r65785 to bytearray.
(easy) patch attached, needs approval!

--
files: bytes-split.patch
keywords: needs review, patch
messages: 71779
nosy: amaury.forgeotdarc
severity: normal
status: open
title: Memory leak in bytes.split()
versions: Python 3.0
Added file: http://bugs.python.org/file11222/bytes-split.patch

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3564] making partial functions comparable

[Terry J. Reedy]

Terry J. Reedy <[EMAIL PROTECTED]> added the comment:

The default equality comparison of Python objects is by id.
Some classes override this, others, in particular, functions, do not.
I also agree that partial functions should not either.

However, you can subclass functools.partial (I checked in 3.0b2) and add
__eq__ and __ne__ methods that implement the definition *you* need, even
if it gives the 'wrong' result of Antoine example.

--
nosy: +tjreedy
resolution:  -> rejected
status: open -> closed

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3650] Memory leak in bytes.split()

[Benjamin Peterson]

Benjamin Peterson <[EMAIL PROTECTED]> added the comment:

Go ahead.

--
nosy: +benjamin.peterson

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3577] Interpreter name: python vs. python-3.0

[Terry J. Reedy]

Changes by Terry J. Reedy <[EMAIL PROTECTED]>:


--
nosy: +tjreedy

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3579] Faites Attention en Utilisant Cette Merveille!

[Terry J. Reedy]

Changes by Terry J. Reedy <[EMAIL PROTECTED]>:


Removed file: http://bugs.python.org/file11139/unnamed

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3579] Faites Attention en Utilisant Cette Merveille!

[Terry J. Reedy]

Changes by Terry J. Reedy <[EMAIL PROTECTED]>:


___
Python tracker <[EMAIL PROTECTED]>

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

[issue3579] SPAM

[Terry J. Reedy]

Changes by Terry J. Reedy <[EMAIL PROTECTED]>:


--
title: Faites Attention en Utilisant Cette Merveille! -> SPAM

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3650] Memory leak in bytes.split()

[Amaury Forgeot d'Arc]

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment:

Committed r65985

--
resolution:  -> fixed
status: open -> closed

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3651] eval() leaks 1 reference every time

[Amaury Forgeot d'Arc]

New submission from Amaury Forgeot d'Arc <[EMAIL PROTECTED]>:

version 3.0, any call to eval() leaks one reference:

>>> eval('1')
1
[42093 refs]
>>> eval('1')
1
[42094 refs]
>>> eval('1')
1
[42095 refs]
>>> eval('1')
1
[42096 refs]

--
components: Interpreter Core
messages: 71783
nosy: amaury.forgeotdarc
priority: release blocker
severity: normal
status: open
title: eval() leaks 1 reference every time
versions: Python 3.0

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3651] eval() leaks 1 reference every time

[Christian Heimes]

Christian Heimes <[EMAIL PROTECTED]> added the comment:

The error is inside compile, not eval:

>>> compile("1", "test", "eval")
 at 0x7ffe1ce2ed50, file "test", line 1>
[43379 refs]
>>> compile("1", "test", "eval")
 at 0x7ffe1ce2e3b0, file "test", line 1>
[43380 refs]
>>> compile("1", "test", "eval")
 at 0x7ffe1ce2ed50, file "test", line 1>
[43381 refs]
>>> compile("1", "test", "eval")
 at 0x7ffe1ce2e3b0, file "test", line 1>
[43382 refs]

--
nosy: +christian.heimes

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3651] eval() leaks 1 reference every time

[Amaury Forgeot d'Arc]

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment:

The leaked reference refers to the bytes object which encodes the code
being compiled:
>>> for x in range(1000): compile("1", "test", "eval")
>>> sys.getrefcount(b'1')
1004

___
Python tracker <[EMAIL PROTECTED]>

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

[issue1396825] subprocess: wait for a period of time

[gd2shoe]

gd2shoe <[EMAIL PROTECTED]> added the comment:

This is just common sense.  I'm trying to avoid a poll() busy-wait
section of code.  I'll figure it out, but it would be much, much easier
if wait accepted a number of seconds, and returned None if the process
was still going (cf. Popen.poll() ).

I'm much happier with subprocess than os.popen*.  I'm also glad that
Popen.kill() is slated for 3.0 .

Since this isn't in the 3.0b3 documentation, I assume this either isn't
fixed or planned?  Are there implementation difficulties?

--
nosy: +gd2shoe

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3636] Managing dual 2.x and 3.0 installations on Windows

[Terry J. Reedy]

Changes by Terry J. Reedy <[EMAIL PROTECTED]>:


--
nosy: +tjreedy

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3651] eval() leaks 1 reference every time

[Benjamin Peterson]

Benjamin Peterson <[EMAIL PROTECTED]> added the comment:

Could it be related to the fact that test_bytes is leaking?

test_bytes leaked [129, 129, 129, 129] references, sum=516

--
nosy: +benjamin.peterson

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3651] eval() leaks 1 reference every time

[Christian Heimes]

Christian Heimes <[EMAIL PROTECTED]> added the comment:

Good point! It's leaking even more on my 64bit machine:

test_bytes leaked [195, 195, 195, 195] references, sum=780

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3651] eval() leaks 1 reference every time

[Amaury Forgeot d'Arc]

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment:

Benjamin: yes, test_bytes calls eval() 128 times.
Christian: please "svn up", I just corrected another leak in bytesobject.c

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3651] eval() leaks 1 reference every time

[Christian Heimes]

Christian Heimes <[EMAIL PROTECTED]> added the comment:

I was already up to date. r65985 leaks 195 references in each run on my box.

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3651] eval() leaks 1 reference every time

[Amaury Forgeot d'Arc]

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment:

The attached patch corrects the eval() and compile() reference leak.
The problem is in PyObject_AsReadBuffer.

Needs review: view->obj seems to own the reference, but object.h say the
opposite.

--
keywords: +needs review, patch
Added file: http://bugs.python.org/file11223/buffer-leak.patch

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3651] eval() leaks 1 reference every time

[Amaury Forgeot d'Arc]

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment:

PyObject_AsCharBuffer is affected as well.
This fixes for me the last refleak in test_bytes.

Added file: http://bugs.python.org/file11224/buffer-leak.patch

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3651] eval() leaks 1 reference every time

[Amaury Forgeot d'Arc]

Changes by Amaury Forgeot d'Arc <[EMAIL PROTECTED]>:


Removed file: http://bugs.python.org/file11223/buffer-leak.patch

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3611] invalid exception context

[Amaury Forgeot d'Arc]

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment:

Benjamin,

I am testing the patch proposed earlier by Victor in
http://bugs.python.org/msg71579 (who might be the correct one, after all),
and I don't see the problems you mentioned. 
I run the test suite without problem, on winXP & Linux Debian x86.

Can you please try again?

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3611] invalid exception context

[Benjamin Peterson]

Benjamin Peterson <[EMAIL PROTECTED]> added the comment:

I can't reproduce it either. I suspect that I removed the wrong lines
initially and caused other problems. :) Sorry for the false alarm.

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3651] eval() leaks 1 reference every time

[Amaury Forgeot d'Arc]

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment:

Of course, I forgot PyObject_AsWriteBuffer in my patch.

I wonder if turning view.obj into an owned reference was a good idea.
There are more calls to bf_getbuffer (in getarg.c), they leak too: 

test_struct leaked [5, 5, 5, 5] references, sum=20

because of a PyArg_ParseTuple with s# and a bytes object.

Added file: http://bugs.python.org/file11225/buffer-leak.patch

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3651] eval() leaks 1 reference every time

[Amaury Forgeot d'Arc]

Changes by Amaury Forgeot d'Arc <[EMAIL PROTECTED]>:


Removed file: http://bugs.python.org/file11224/buffer-leak.patch

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3651] eval() leaks 1 reference every time

[Amaury Forgeot d'Arc]

Changes by Amaury Forgeot d'Arc <[EMAIL PROTECTED]>:


--
assignee:  -> loewis
nosy: +loewis

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3625] test issues on 64bit windows

[Mark Hammond]

Mark Hammond <[EMAIL PROTECTED]> added the comment:

Thanks.  Checked into the trunk in r65986

--
resolution:  -> fixed
status: open -> closed

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3652] Remove DeprecationWarning in _warnings about 'line'

[Brett Cannon]

New submission from Brett Cannon <[EMAIL PROTECTED]>:

The DeprecationWarning introduced in Python 2.6/3.0 about the 'line'
argument for showwarning() can be removed in 2.7/3.1.

--
assignee: brett.cannon
components: Library (Lib)
messages: 71797
nosy: brett.cannon
priority: normal
severity: normal
status: open
title: Remove DeprecationWarning in _warnings about 'line'
type: behavior
versions: Python 2.7, Python 3.1

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3602] Move test.test_suport.catch_warning() to the 'warnings' module

[Brett Cannon]

Brett Cannon <[EMAIL PROTECTED]> added the comment:

The patch does a couple of things. It moves
test.test_support.catch_warning() to warnings.catch_warnings() and
leaves a stub behind. WarningsRecorder becomes a subclass of list to
make it easier to work with. The uses of catch_warnings() in the stdlib
are moved to the 'warnings' implementation along with protecting the
warnings filter changes behind a sys.py3kwarning 'if' statement. And
finally, a oversight in the triggering of a DeprecationWarning for
showwarning() and the new 'line' argument has been fixed (with the
appropriate test).

--
assignee: brett.cannon -> 
keywords: +needs review, patch
Added file: http://bugs.python.org/file11226/move_catch_warnings.diff

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3640] test_cpickle crash on AMD64 Windows build

[Mark Hammond]

Mark Hammond <[EMAIL PROTECTED]> added the comment:

Sorry for the initial noise - your analysis is correct, mine was flawed
:)  Simple recursion to a depth of 1000 does work fine on a 64bit build.

cpickle.patch does make test_cpickle pass for me.  FWIW,
find_recursionlimit.py now causes a segfault on 32 and 64bit Windows
(the comments imply a MemoryError is expected there), and the 32bit
version dies at a depth of 5900, while the 64bit version dies at 3800
(both doing an 'add') - so it does seem there is still a discrepancy -
but not one we need to care about now.

I'm +1 in general on this, but I'm not sure that I'm +1 on this patch
for 1.6 without more careful review than I am able to offer at the
moment; it seems fairly unlikely to be hit "in the wild", but I'll
obviously defer that to others.  OTOH, having the test suite segfault
isn't a good look, so we probably need to do *something* for 1.6

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3602] Move test.test_suport.catch_warning() to the 'warnings' module

[Benjamin Peterson]

Benjamin Peterson <[EMAIL PROTECTED]> added the comment:

See my comments on Rietveld. http://codereview.appspot.com/3255

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3566] httplib persistent connections violate MUST in RFC2616 sec 8.1.4.

[Mark Hammond]

Changes by Mark Hammond <[EMAIL PROTECTED]>:


--
nosy: +mhammond

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3602] Move test.test_suport.catch_warning() to the 'warnings' module

[Brett Cannon]

Changes by Brett Cannon <[EMAIL PROTECTED]>:


Added file: http://bugs.python.org/file11227/move_catch_warnings.diff

___
Python tracker <[EMAIL PROTECTED]>

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

[issue3602] Move test.test_suport.catch_warning() to the 'warnings' module

[Brett Cannon]

Brett Cannon <[EMAIL PROTECTED]> added the comment:

New patch is up with a minor change from Benjamin's review. My explicit
comments on the suggestions are on Rietveld.

___
Python tracker <[EMAIL PROTECTED]>

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