Changes by Martin v. Löwis :
--
components: +2to3 (2.x to 3.0 conversion tool)
___
Python tracker
<http://bugs.python.org/issue4662>
___
___
Python-bugs-list m
Changes by Martin v. Löwis :
--
components: +2to3 (2.x to 3.0 conversion tool) -Library (Lib)
___
Python tracker
<http://bugs.python.org/issue6409>
___
___
Pytho
Martin v. Löwis added the comment:
Benjamin, ISTM that the tests in lib2to3/tests/data/py2_test_grammar aren't run
at all, as part of regrtest. If so, the entire file could be removed.
--
components: +Installation -2to3 (2.x to 3.0 conversion
Martin v. Löwis added the comment:
I've ported the program to Linux (see attached tar file). I cannot observe any
memory leak here - even if I let the program run for a long time (linking with
Python 2.6). Memory usage in top goes up and down, but never over some upper
limit.
The
Martin v. Löwis added the comment:
1. I agree that we should fix the unlinking problem on Windows. I also think
that such a fix should be independent of the test suite - many people run into
failed unlink problems.
2. Tim already said it, but I repeat: the common theory is that the culprit
Martin v. Löwis added the comment:
> I'm afraid that the problem doesn't lie in the unlink: DeleteFile
> succeeds. The problem is that the file is only marked for delete
> until such time as the last SHARE_DELETE handle on it is closed.
Then we shouldn't use DeleteFi
Martin v. Löwis added the comment:
I can't reproduce the problem on Windows, either. The attached project runs the
thread creation in a loop (leaving the 3s sleep in the code). I see (in process
viewer) that the Commit Size varies between 13MB and 14MB; there is no
indication of a
Martin v. Löwis added the comment:
> Would you agree that py3k is the only target branch worth aiming for?
Most certainly, yes.
--
___
Python tracker
<http://bugs.python.org/iss
Martin v. Löwis added the comment:
Ok, it consumes more memory - why do you think there is a leak?
--
___
Python tracker
<http://bugs.python.org/issue8
Martin v. Löwis added the comment:
getdefaultlocale is inherently unmaintainable, and shouldn't be used by
applications. I wish it was removed from Python (but unfortunately, too many
people got tricked into believing that it does something useful).
That said, if anybody feels like upd
Martin v. Löwis added the comment:
> Can we tell about getdefaultlocale’s uselessness in the docs?
I haven't quite understood what people want to use that function for. If
we knew the typical use cases, we could make recommendations what they
should use instead.
One use case is to
Martin v. Löwis added the comment:
> When the table is updated in trunk, can it be backported to 2.6?
With the changes to the encodings for some of the locales (e.g. 'ru'), I
would advise against such a backport.
This also demonstrates one fundamental flaw of the approach: even i
Martin v. Löwis added the comment:
The patch in file16727 was applied as part of issue8316.
--
___
Python tracker
<http://bugs.python.org/issue8279>
___
___
Pytho
Martin v. Löwis added the comment:
I have now applied file16808 as r79986. I'm detaching file16804, as it was
superceded by the other patch. I also reenabled all tests in r79987, to see how
the buildbots react.
--
___
Python tracker
Martin v. Löwis added the comment:
> getdefaultlocale() provides a way to access the default locale
> (and encoding) on a platform without requiring a call to
> setlocale(LC_ALL, "")
That's what it's meant to do, but this is not what it actually does.
In fact, t
Martin v. Löwis added the comment:
> Maybe the state of this discussion is my fault for not being clear
> enough. Let's abandon terms such as "broken" and "roundrobin." CS
> theory has the perfectly useful terms "fair" and "unfair.&qu
Martin v. Löwis added the comment:
pitrou: I agree, it should be a TypeError.
--
nosy: +loewis
___
Python tracker
<http://bugs.python.org/issue8401>
___
___
Pytho
Changes by Martin v. Löwis :
--
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue8344>
___
___
Python-bugs-list mailing list
Unsubscri
Martin v. Löwis added the comment:
Notice that 2.7 has seen its first beta release, so no new features are allowed
for it. I think it's better to target this feature for 3.2.
--
nosy: +loewis
___
Python tracker
<http://bugs.python.org/i
Martin v. Löwis added the comment:
Dave, file 16727 fails to apply, but apparently still contains necessary
pieces. Can you please provide an updated version of the patch against the
trunk?
--
___
Python tracker
<http://bugs.python.org/issue8
Martin v. Löwis added the comment:
> On pthreads plaforms, if the posix_sem functions aren't available
> (when _POSIX_SEMAPHORES isn't defined), the python lock is
> implemented with a mutex and a condition variable. This appears to
> be the case on Mac OS X, for exampl
Martin v. Löwis added the comment:
-1 on assigning strings to slices of bytearrays. As Ezio mentions, this
operation conceptually requires an encoding, and no encoding is readily
available in the slice assignment.
-1 on special-casing empty strings
Martin v. Löwis added the comment:
David, can you take a look?
--
nosy: +db3l, loewis
___
Python tracker
<http://bugs.python.org/issue8421>
___
___
Python-bug
Changes by Martin v. Löwis :
--
keywords: +buildbot
___
Python tracker
<http://bugs.python.org/issue8422>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Martin v. Löwis :
--
keywords: +buildbot
___
Python tracker
<http://bugs.python.org/issue8423>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Martin v. Löwis :
--
keywords: +buildbot
___
Python tracker
<http://bugs.python.org/issue8424>
___
___
Python-bugs-list mailing list
Unsubscribe:
Martin v. Löwis added the comment:
Thanks for the patch, committed as r80156. As expected, there are still
complaints about gdb.Frame.
As the original issue is now resolved, I'm closing this issue as fixed, and
open a new issue for the remaining failures.
--
resolution: -&g
New submission from Martin v. Löwis :
I get a number of failures in test_gdb with gdb 7.0.1 about gdb.Frame, e.g.
FAIL: test_basic_command (test.test_gdb.PyListTests)
Verify that the "py-list" com
Martin v. Löwis added the comment:
Victor, please leave that to David. He will fix it.
--
___
Python tracker
<http://bugs.python.org/issue8437>
___
___
Python-bug
Martin v. Löwis added the comment:
-1 on backporting. The handler isn't really meant to be used in applications,
plus 2.7 is in feature-freeze.
--
___
Python tracker
<http://bugs.python.org/i
Martin v. Löwis added the comment:
> Since 2.7 is meant to be the last release of the 2.x series,
> we have to make sure that it has all the bits necessary to make
> porting apps to 3.x easy.
Any new features in 2.7 require approval from the release ma
Martin v. Löwis added the comment:
Duplicate of #8442
--
nosy: +loewis
resolution: -> duplicate
status: open -> closed
superseder: -> Broken zipfile with python 3.2 on osx
___
Python tracker
<http://bugs.python.o
Martin v. Löwis added the comment:
> Martin, I don't know if you were suggesting that a "fair" mutex would
> make the emulated semaphore fair too. You probably weren't, but just
> in case, the fairness of the mutex is immaterial because it is only
> held for a
Martin v. Löwis added the comment:
> Martin, I´ve explained it in my other dissue, issue 8411, with a step by step
> example.
Hmm. Can't find it there. What message or file should I be looking at?
--
___
Python tracker
<http://b
New submission from Martin v. Löwis :
The current build_installer fails to build dependencies, e.g. with
gcc-4.0 -arch i386 -arch ppc -isysroot /Developer/SDKs/MacOSX10.4u.sdk -o
bzip2 bzip2.o -L. -lbz2
collect2: cannot find 'ld'
collect2: cannot find 'ld'
lipo: can
Martin v. Löwis added the comment:
David Bolen reported that this occurs with r80179, which now clears the PATH
environment variable, removing ld from the path.
--
___
Python tracker
<http://bugs.python.org/issue8
Martin v. Löwis added the comment:
Folks, can we please focus at one issue at a time? I'm not sure I understand
the issue that this patch is supposed to fix; in any case, I can report that it
doesn't fix *this* issue. I'm still getting the very same failures after
applying the
Martin v. Löwis added the comment:
I personally can't verify what version of Xcode is installed. David?
In any case, David reported that he could build installers just fine on that
very machine before r80179, but not after.
--
nosy:
Martin v. Löwis added the comment:
I haven't reviewed the patch in detail yet, but it seems to me that it fixes
independent issues. -1000 on that. One problem, one bug report in the tracker,
one commit.
If this issue is about the import machinery not working anymore if there is a
non-
Martin v. Löwis added the comment:
That fixes it indeed, see
http://www.python.org/dev/buildbot/builders/2.7.dmg/builds/11/steps/compile/logs/stdio
As for "which shell is being used": the slave reports that in his environment,
there is
SHELL=/bin/bash
Not sure whether this actu
Changes by Martin v. Löwis :
--
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue8453>
___
___
Python-bugs-list
Martin v. Löwis added the comment:
I'm attaching the full output. It's the same as the one in the original report
(msg103442) still.
--
Added file: http://bugs.python.org/file17011/test_gdb.txt
___
Python tracker
<http://bugs.python.
Martin v. Löwis added the comment:
Amaury, I fail to see how the error you get on Windows is related to this
issue. AFAICT, neither the issue nor the patch affects Windows at all.
Closing the issue as fixed.
If you think there is also an issue on Windows, please submit a new bug report
Martin v. Löwis added the comment:
Amaury, I'm closing this for the same reason I explained in msg103745
--
nosy: +loewis
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python
Martin v. Löwis added the comment:
Yes, I did try with version 3.
--
___
Python tracker
<http://bugs.python.org/issue8437>
___
___
Python-bugs-list mailin
Martin v. Löwis added the comment:
> Do you have an old python-gdb.py file in your Python root directory?
Ah, ok. That was the problem indeed. The patch actually works fine.
--
___
Python tracker
<http://bugs.python.org/iss
New submission from Martin v. Löwis :
test_gdb currently fails on 3k; some tests with a "No stack" message. I'll
attach the full output, but would like this issue to focus on the "No stack"
failures.
--
files: test_gdb.txt
messages: 103802
nosy: loewis
seve
Changes by Martin v. Löwis :
--
assignee: -> dmalcolm
nosy: +dmalcolm
___
Python tracker
<http://bugs.python.org/issue8479>
___
___
Python-bugs-list mai
New submission from Martin v. Löwis :
test_gdb fails on 3k; some tests with a message "Error occurred in Python
command: No frame is currently selected."
A separate problem was reported as #8479; I'm attaching the full test_gdb
output.
--
assignee: dmalcolm
file
Changes by Martin v. Löwis :
--
assignee: -> dmalcolm
___
Python tracker
<http://bugs.python.org/issue8482>
___
___
Python-bugs-list mailing list
Unsubscri
Martin v. Löwis added the comment:
That patch makes no sense. According to SSL_library_init(3SSL),
"OpenSSL_add_ssl_algorithms() and SSLeay_add_ssl_algorithms() are synonyms for
SSL_library_init()"
So it shouldn't really matter which of these you call, and it should be
suf
Martin v. Löwis added the comment:
I'm in favor of removing that support, too, but please check with python-dev
whether anybody thinks a proper deprecation cycle (deprecated in 3.2, removed
in 3.3) is needed.
--
___
Python tracker
Martin v. Löwis added the comment:
Victor's patch look fine to me (at least, I can't see a problem with it). If
so, we should keep it.
In any case, it does fix the problem reported here.
--
___
Python tracker
<http://bugs.python.
Martin v. Löwis added the comment:
> The patch calls OpenSSL_add_all_algorithms(), though.
Ah, ok. The patch looks fine to me, then.
--
title: ssl socket with certificate verification fails on SHA256 digest
algorithm -> ssl socket with certificate verification fails on
Martin v. Löwis added the comment:
See msg103889. I said it's fixed, so I'm not sure what problem you are still
trying to solve.
--
___
Python tracker
<http://bugs.python.
Martin v. Löwis added the comment:
Thanks for the patch; applied as r80324. As it is an improvement over the
status quo, I've applied it; I'll also be closing this issue.
I still get test failures which I report as a separate bug report.
As for displaying strings: I think it shou
New submission from Martin v. Löwis :
test_gdb fails on 3k, with the attached output.
--
assignee: dmalcolm
files: test_gdb.txt
messages: 103919
nosy: dmalcolm, loewis
severity: normal
status: open
title: test_gdb assertEndsWith failing
versions: Python 3.2
Added file: http
Martin v. Löwis added the comment:
I think the "replace" handler would be more appropriate here.
--
___
Python tracker
<http://bugs.python.org/issue8495>
___
__
Martin v. Löwis added the comment:
Thanks for the patch. Committed as r80355-
--
nosy: +loewis
___
Python tracker
<http://bugs.python.org/issue8475>
___
___
Pytho
Martin v. Löwis added the comment:
It seems to work fine, so merged as r80365, r80366, r80367.
--
resolution: -> accepted
status: open -> closed
___
Python tracker
<http://bugs.python.org/
Martin v. Löwis added the comment:
Jesus, any idea?
--
assignee: -> jcea
nosy: +jcea, loewis
___
Python tracker
<http://bugs.python.org/issue8504>
___
___
Py
Martin v. Löwis added the comment:
Peter, please stay out of this bug report unless you are certain that you have
the very problem that the OP reported, namely that a database created by Python
2.5 cannot be imported in 2.6. I'm taking the performance issues out of this
bug report; an
Martin v. Löwis added the comment:
I just noticed that Tim reports in msg104030 that the original problem is
resolved. So I'm closing this report as fixed.
If you create a new one on the performance issue, please make sure to include a
repeatable test case, with instructions on how to r
Changes by Martin v. Löwis :
--
resolution: -> invalid
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue8504>
___
___
Python-bugs-
Martin v. Löwis added the comment:
I don't think Python 2.7 should upgrade to a newer autoconf version at this
point. For 3.2, we could try it out.
--
nosy: +loewis
___
Python tracker
<http://bugs.python.org/i
Martin v. Löwis added the comment:
MSI short names must be 8.3 names. Microsoft has them in MSI in case the MSI
file gets installed on an 8.3 system, or in case 8.3 applications want to
access files and want to be sure they access the right one. So the actual
numbering is completely
Martin v. Löwis added the comment:
You can have at most one CAB object per database, yes. However, you can have
certainly multiple cab files in the installer; just call add_data yourself.
If you are using the API provided by msilib, there should be no need to ever
have more than one CAB
Martin v. Löwis added the comment:
I still don't see the need to create multiple CABs. Just use the Directory
class to add files, and that will automatically record them in the singleton
CAB.
--
___
Python tracker
<http://bugs.py
Martin v. Löwis added the comment:
> First question: Open a new issue, or discuss it in this one (and repoen it)?
Please open a new issue. AFAICT, the original issues request (do not
embed manifests in pyd files) is now implemented fully. Feel free to
leave a link to the new issue here,
New submission from Martin v. Löwis :
What is the default priority?
--
messages: 104274
nosy: loewis
severity: normal
status: open
title: Test issue
___
Python tracker
<http://bugs.python.org/issue8
Changes by Martin v. Löwis :
--
resolution: -> rejected
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue8541>
___
___
Python-bugs-
New submission from Martin v. Löwis :
What is the priority now?
--
messages: 104275
nosy: loewis
priority: normal
severity: normal
status: open
title: Another test issue
___
Python tracker
<http://bugs.python.org/issue8
Changes by Martin v. Löwis :
--
resolution: -> accepted
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue8542>
___
___
Python-bugs-
Changes by Martin v. Löwis :
--
priority: -> normal
___
Python tracker
<http://bugs.python.org/issue1404>
___
___
Python-bugs-list mailing list
Unsubscri
Changes by Martin v. Löwis :
--
priority: -> normal
___
Python tracker
<http://bugs.python.org/issue1601>
___
___
Python-bugs-list mailing list
Unsubscri
Changes by Martin v. Löwis :
--
priority: -> normal
___
Python tracker
<http://bugs.python.org/issue3947>
___
___
Python-bugs-list mailing list
Unsubscri
Changes by Martin v. Löwis :
--
priority: -> normal
___
Python tracker
<http://bugs.python.org/issue5249>
___
___
Python-bugs-list mailing list
Unsubscri
Changes by Martin v. Löwis :
--
priority: -> normal
___
Python tracker
<http://bugs.python.org/issue5273>
___
___
Python-bugs-list mailing list
Unsubscri
Changes by Martin v. Löwis :
--
priority: -> normal
___
Python tracker
<http://bugs.python.org/issue5334>
___
___
Python-bugs-list mailing list
Unsubscri
Changes by Martin v. Löwis :
--
priority: -> normal
___
Python tracker
<http://bugs.python.org/issue6150>
___
___
Python-bugs-list mailing list
Unsubscri
Changes by Martin v. Löwis :
--
priority: -> normal
___
Python tracker
<http://bugs.python.org/issue6453>
___
___
Python-bugs-list mailing list
Unsubscri
Changes by Martin v. Löwis :
--
priority: -> normal
___
Python tracker
<http://bugs.python.org/issue7540>
___
___
Python-bugs-list mailing list
Unsubscri
Martin v. Löwis added the comment:
Closing it as "won't fix": nobody is really interested in working on the
problem.
--
resolution: -> wont fix
status: open -> closed
___
Python tracker
<http://b
Martin v. Löwis added the comment:
> Another reason to allow multiple CAB files in a single installer?
I'm still curious as to what the first reason is.
--
___
Python tracker
<http://bugs.python.or
Martin v. Löwis added the comment:
You could also try to commit the MSI file in-between, which may release memory.
--
___
Python tracker
<http://bugs.python.org/issue8
Martin v. Löwis added the comment:
IIUC, Python is not affected by this security issue. 'short' is a 16-bit
integer, so it only affects 0.9.8m, which isn't being used by Python.
Therefore, from a security point of view, no action needs to be taken.
I don't think
Changes by Martin v. Löwis :
--
priority: critical -> normal
___
Python tracker
<http://bugs.python.org/issue8569>
___
___
Python-bugs-list mailing list
Un
Changes by Martin v. Löwis :
--
resolution: wont fix -> out of date
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue1533>
___
___
Pyth
Martin v. Löwis added the comment:
I really, really, REALLY think that it is bad to mix issues. This makes patch
review impossible.
This specific issue is about introducing an fsdecode and fsencode function;
this is what the bug title says, and what the initial patch did.
Whether or not
Martin v. Löwis added the comment:
> I think that we cannot decide correctly about fs*code() until we decided for
> os.environb.
Why is that? In msg104063, you claim that you want to create these
functions to deal with file names (not environment variables), in
msg104064, you claim that
Martin v. Löwis added the comment:
Can somebody please explain what problem is being solved with this patch?
--
___
Python tracker
<http://bugs.python.org/issue8
Martin v. Löwis added the comment:
I think it is helpful to read the pax specification here:
http://www.opengroup.org/onlinepubs/009695399/utilities/pax.html
pax defines (IIUC) that all strings in a pax-compliant tar file are UTF-8
encoded. For the "invalid" option, they
Martin v. Löwis added the comment:
STINNER Victor wrote:
> STINNER Victor added the comment:
>
>> Why is that? In msg104063, you claim that you want to create these
>> functions to deal with file names (not environment variables)
>
> Yes, but my os_path_fs_encode_d
Changes by Martin v. Löwis :
--
nosy: +loewis
___
Python tracker
<http://bugs.python.org/issue8606>
___
___
Python-bugs-list mailing list
Unsubscribe:
Martin v. Löwis added the comment:
> Please see the discussion on http://bugs.python.org/issue8514
> for details.
I can't see any report of actual breakage in that report, only claims of
potential breakage (with no supporti
Martin v. Löwis added the comment:
> An issue was opened 2 years ago: "It was brought up in a discussion
> of sending non-ASCii data to a CGI-WSGI script where the data would
> be transferred via os.environ." => #4006 (closed as "wont fix").
Fortunately, that is
Martin v. Löwis added the comment:
> Set your CODESET to ASCII and watch the surrogate escaping
> begin... seriously, Martin, if you've ever worked with CGI
> or WSGI or FastCGI or SCGI or any of the many other protocols
> that use the OS environment for passing data betwee
Martin v. Löwis added the comment:
> Here's one (RFC 3875, sections 4.1.7 and 4.1.5):
>
> LANG = 'en_US.utf8'
> CONTENT_TYPE = 'application/x-www-form-urlencoded'
> QUERY_STRING = 'type=example&name=Löwis'
> PATH_INFO = '/home/lÃ
Martin v. Löwis added the comment:
> Your name will end up being partially escaped as surrogate:
>
> 'L\udcf6wis'
>
> Further processing will fail
That depends on the further processing, no?
> Traceback (most recent call last):
> File "", line 1,
Martin v. Löwis added the comment:
> Using os.getenvb(), you can decode the string using the right
> encoding (which may be different for each variable).
Ok. If that's the motivation, the documentation should make that
clear (there isn't any documentation in the patch, anyw
1701 - 1800 of 4778 matches
Mail list logo