Martin v. Löwis [EMAIL PROTECTED] added the comment:
As a further follow-up, I have now looked at the log file, and the
problematic lines are
MSI (s) (DC:40) [10:44:39:425]: Ignoring disallowed property TARGETDIR
MSI (s) (DC:40) [10:44:39:425]: Ignoring disallowed property DLLDIR
Try setting
Martin v. Löwis [EMAIL PROTECTED] added the comment:
FWIW, this is fixed in Python 3.0.
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2481
__
___
Python-bugs-list mailing list
Martin v. Löwis [EMAIL PROTECTED] added the comment:
Sure, although it probably shouldn't be backported to 2.5.
--
versions: +Python 2.6 -Python 2.5
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2481
Martin v. Löwis [EMAIL PROTECTED] added the comment:
Why does it improve portability to use stdbool.h when it exists?
What is the potential issue with asdl.c that gets fixed with this patch?
--
nosy: +loewis
__
Tracker [EMAIL PROTECTED]
http
Martin v. Löwis [EMAIL PROTECTED] added the comment:
Some compilers define false and true as macros.
Which compilers specifically? It sounds like a violation of the C
standard to do so, without stdbool.h being included.
Using stdbool.h when it is available will ensure bool is defined
Martin v. Löwis [EMAIL PROTECTED] added the comment:
If stdbool is not available, C99 still defines false and true as macros.
What do you mean by that? In C99, true and false are *not* defined in
a translation unit unless stdbool.h is included, see 7.16.
If stdbool is available, then most
Martin v. Löwis mar...@v.loewis.de added the comment:
This is a duplicate of issue1616979.
--
nosy: +loewis
resolution: - duplicate
status: open - closed
superseder: - cp720 encoding map
___
Python tracker rep...@bugs.python.org
http
Martin v. Löwis mar...@v.loewis.de added the comment:
Please trust me that this *is* a duplicate issue.
This bug tracker is not a place to get help; it is a place to report bugs. The
bug you are reporting has been reported before. Other duplicate reports are
#6995, #7496, #7600, #8120
Martin v. Löwis mar...@v.loewis.de added the comment:
Can you propose a patch?
--
nosy: +loewis
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8695
Martin v. Löwis mar...@v.loewis.de added the comment:
I think it's important to note that this may err towards larger numbers (rather
than being merely inaccurate).
I also find this an upper bound on ratio() difficult to understand. IIUC, it
is the correct value being bounded, not the result
Changes by Martin v. Löwis mar...@v.loewis.de:
--
priority: normal - low
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue3621
___
___
Python-bugs
Martin v. Löwis mar...@v.loewis.de added the comment:
haypo: what's the relationship?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8678
Martin v. Löwis mar...@v.loewis.de added the comment:
I have retired the user Jack.Diederich.
In the future, please use the meta tracker to discuss issues with this tracker.
--
nosy: +loewis -Jack.Diederich
___
Python tracker rep...@bugs.python.org
Martin v. Löwis mar...@v.loewis.de added the comment:
Why do you think this is a bug in Python? It rather sounds like you
misconfigured your system somehow. Without access to the system, it is
difficult to guess what the misconfiguration might be, though.
--
nosy: +loewis
Martin v. Löwis mar...@v.loewis.de added the comment:
I am new to this help system
Please understand that this is not a help system at all.
Instead, it is a bug tracker: a way for people to contribute
to Python, by reporting bugs or contributing code. For help,
please contact one of the Python
Martin v. Löwis mar...@v.loewis.de added the comment:
It's fine to apply to 3.2.
--
nosy: +loewis
resolution: - accepted
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8761
Martin v. Löwis mar...@v.loewis.de added the comment:
Doesn't breaking installation of packages on a major platform warrant a
quicker release of a fix?
No, only security-related issues may warrant a change to the release
schedule.
--
title: distutils makefile from python.org
Martin v. Löwis mar...@v.loewis.de added the comment:
I think there is harm in removing this block; it would cause PY_LONG_LONG not
to be defined anymore. Closing as invalid.
--
resolution: - invalid
status: open - closed
___
Python tracker rep
Changes by Martin v. Löwis mar...@v.loewis.de:
--
versions: +Python 3.2 -Python 2.7, Python 3.1
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1445781
Martin v. Löwis mar...@v.loewis.de added the comment:
[The original link seems down; I found a similar description at
http://msdn.microsoft.com/en-us/library/aa372049%28VS.85%29.aspx]
I think you are misinterpreting the documentation. It doesn't say that the
codepage property is required
Martin v. Löwis mar...@v.loewis.de added the comment:
I fail to see the bug in this report. As you found out, you need to set the
codepage property before setting any of the string properties. This is a
requirement imposed by Microsoft, and has nothing to do with Python.
--
resolution
Changes by Martin v. Löwis mar...@v.loewis.de:
--
versions: +Python 3.2 -Python 2.7, Python 3.1
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1542
Changes by Martin v. Löwis mar...@v.loewis.de:
--
versions: +Python 3.2 -Python 2.7, Python 3.1
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1566260
Martin v. Löwis mar...@v.loewis.de added the comment:
I think that we should use the locale encoding to encode and decode command
line arguments.
I disagree. IIUC, this is only about OSX. Now, we shouldn't take any
action until either some OSX expert explains us how command line
arguments
Martin v. Löwis mar...@v.loewis.de added the comment:
As os.environb, it would be useful to have bytes version of sys.argv
to have able to decide the encoding used to decode each argument, or
to manipulate bytes if we don't care about the encoding.
-1. Py_Main expects wchar_t*, so no byte
Martin v. Löwis mar...@v.loewis.de added the comment:
You are mistaken. It doesn't include __path__ into repr, but __file__. It
prints (built-in) if the filename is not set for some reason.
--
nosy: +loewis
resolution: - invalid
status: open - pending
Martin v. Löwis mar...@v.loewis.de added the comment:
Can you please provide a reproducible bug report? I have no idea what paste
is or how it got into your .local folder. Please structure the bug report as
follows:
1. this is what you did
2. this is what happened
3. this is what you expected
Martin v. Löwis mar...@v.loewis.de added the comment:
For other alternatives to the LGPL liblzma, you really don't have
any,
If that's really the case (which I don't believe it is), then this
project stops right here. If the underlying library is LGPL, it would
require us to distribute its
Martin v. Löwis mar...@v.loewis.de added the comment:
Am 26.05.2010 10:51, schrieb Antoine Pitrou:
Antoine Pitroupit...@free.fr added the comment:
If the underlying library is LGPL, it would
require us to distribute its sources along with the Windows binaries,
which I'm not willing to do
Martin v. Löwis mar...@v.loewis.de added the comment:
[Replying to msg106566]
if you're already looking at issue6715, then I don't get why you're
asking.. ;)
Can you please submit a contributor form?
Martin: For LGPL (or even GPL for that matter, disregarding linking
restrictions
Martin v. Löwis mar...@v.loewis.de added the comment:
tsktsk, discussions about python module for xz compression should
anyways be kept at issue6715 as this one is about the tarfile module
;p
Ok, following up there.
--
___
Python tracker rep
Martin v. Löwis mar...@v.loewis.de added the comment:
Can you tell me where you are currently providing the source code for
the readline library, or the gdbm library?
We don't, as they aren't included in the Windows distribution. The
readline library doesn't work on Windows, anyway
Martin v. Löwis mar...@v.loewis.de added the comment:
Can you provide a patch?
--
nosy: +loewis
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8831
Martin v. Löwis mar...@v.loewis.de added the comment:
Thanks for the patch. Committed as r81582 and r81583.
Antoine was right: subsequent references to Solaris needed to be removed also.
--
resolution: - accepted
status: open - closed
___
Python
Martin v. Löwis mar...@v.loewis.de added the comment:
Martin said these codecs are coming back in 3.2.
I think you are confusing me with MAL. I remain opposed to adding them
back. Users ought to use the modules that provide these these
conversions as functions.
--
title: Remove
Martin v. Löwis mar...@v.loewis.de added the comment:
The patch lacks documentation. Otherwise, I think it's fine.
--
nosy: +loewis
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8845
Martin v. Löwis mar...@v.loewis.de added the comment:
Please verify that HAVE_NETPACKET_PACKET_H does indeed get defined, looking at
pyconfig.h.
Please inspect config.log to find out why it does get defined.
--
nosy: +loewis
___
Python tracker rep
Martin v. Löwis mar...@v.loewis.de added the comment:
The AF_PACKET support was original meant for Linux. When Solaris now also
supports that socket family, and with a similar interface, it might be
interesting to port that support to Solaris.
If nobody volunteers, it might be easier
Martin v. Löwis mar...@v.loewis.de added the comment:
This shouldn't be necessary. If a 32-bit Python looks into the registry, it
will get automatically redirected to Wow6432Node. If a 64-bit Python looks into
the registry, it shouldn't have any interest in values stored in Wow6432Node
Martin v. Löwis mar...@v.loewis.de added the comment:
What operating system is this on? What exact Python version are you using?
I can't reproduce this with r81614 on Linux.
--
nosy: +loewis
___
Python tracker rep...@bugs.python.org
http
Martin v. Löwis mar...@v.loewis.de added the comment:
Defining _XPG4_2 is surely the wrong thing to do, right? It's an internal flag
only, not meant to be used by applications.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org
Martin v. Löwis mar...@v.loewis.de added the comment:
Most likely, we wouldn't be able to support recvmsg on Solaris. We would need
to run configure tests to determine whether the APIs are available, and that
would require defining _XOPEN_SOURCE in pyconfig.h.in, which (according to
#1759169
Martin v. Löwis mar...@v.loewis.de added the comment:
Just in case it isn't clear: this is because of the order of fixes. The first
fixer replaces httplib with http.client, then the next fixer thinks this is a
relative import.
--
nosy: +loewis
Martin v. Löwis mar...@v.loewis.de added the comment:
Can somebody please explain how the test and the reported bug are related? The
patch seems to deal with paths that have UNC in them; and the test seems not
to.
--
___
Python tracker rep
Martin v. Löwis mar...@v.loewis.de added the comment:
Also, cgohlke, can you please provide complete, detailed instructions on how to
reproduce this issue? How do I get python.exe into \\Server\Share in the first
place? And why did you not map a network drive letter
Martin v. Löwis mar...@v.loewis.de added the comment:
Applications should not assume a particular length for sun_path or
assume that it can hold {_POSIX_PATH_MAX} characters (255).
hence, it seems to me that python should not actually be doing any size
checks on the path passed
Changes by Martin v. Löwis mar...@v.loewis.de:
--
title: Allow binding to local address in httplib / http.client - Allow binding
to local address in http.client
versions: +Python 3.2 -Python 2.7, Python 3.3
___
Python tracker rep...@bugs.python.org
Martin v. Löwis mar...@v.loewis.de added the comment:
Can you please elaborate? Why would binding be useful?
In any case, what's wrong with 2.7's source_address parameter?
--
nosy: +loewis
___
Python tracker rep...@bugs.python.org
http
Changes by Martin v. Löwis mar...@v.loewis.de:
--
resolution: - out of date
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8884
Martin v. Löwis mar...@v.loewis.de added the comment:
Fixed in r81692, r81694.
--
resolution: - fixed
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8864
Martin v. Löwis mar...@v.loewis.de added the comment:
The patch is now out of date; merge.py got merged into msi.py.
--
resolution: - out of date
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5467
Martin v. Löwis mar...@v.loewis.de added the comment:
This is now fixed in r81697 and r81698.
--
resolution: - fixed
status: open - closed
versions: +Python 3.2 -Python 2.6
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5464
Martin v. Löwis mar...@v.loewis.de added the comment:
Following the python-dev consensus, I have now added a warning to the 2.7
installer that this will be the last release supporting Windows 2000.
I still think that we should not bump the SDK version above 500 for 2.7.
Changing the SDK level
Martin v. Löwis mar...@v.loewis.de added the comment:
Thanks for the patch. Committed as r81701, r81702, r81703 and r81704.
--
resolution: - accepted
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6470
Martin v. Löwis mar...@v.loewis.de added the comment:
The binaries get compiled with the PGInstrument/PGUpdate configurations.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8847
Martin v. Löwis mar...@v.loewis.de added the comment:
ISTM that this report is based on hearsay; nobody is *actually* experiencing
any problems. Proposing to close this as invalid.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org
Changes by Martin v. Löwis mar...@v.loewis.de:
--
resolution: - invalid
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8929
Martin v. Löwis mar...@v.loewis.de added the comment:
7-zip encodes à (U+00e0) as 0x85 (1 byte), and é (U+00e9) as 0x82 (1
byte). I don't know this encoding.
That's an old DOS code paged used in Europe: CP850
There is a good chance that they use it because it is the OEM code page
Martin v. Löwis mar...@v.loewis.de added the comment:
This looks like a glibc bug to me. I suspect an unauthorized redhat change; I
hope Ulrich Drepper would have never accepted a glibc that causes getaddrinfo
to implicitly call setlocale - see
http://sources.redhat.com/ml/libc-alpha/2004-03
Martin v. Löwis mar...@v.loewis.de added the comment:
Assuming you are willing to contribute evpy (and have the rights to do so, i.e.
all of the code is truly yours): what's the user acceptance of the code?
In particular, what do authors of competing OpenSSL wrappers (like M2Crypto) or
other
Martin v. Löwis mar...@v.loewis.de added the comment:
and have the rights to do so, i.e. all of the code is truly yours
Is it really required, or is a non-copyleft liberal license (MIT-like or
BSD-like) enough?
The contributor would have to sign a contributor agreement, giving the
PSF
Changes by Martin v. Löwis mar...@v.loewis.de:
--
title: add encryption/decryption/signature/verification routinesto
stdlib - add crypto routines to stdlib
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8998
Martin v. Löwis mar...@v.loewis.de added the comment:
I (as a programmer) have never seen the specific code for python's
mkdir function, And I have no way to know whether I should presume
that mkdir in python works the same way as the gnu command or not.
Unless it is documented that is.
You
Martin v. Löwis mar...@v.loewis.de added the comment:
Please run python.exe Lib/idlelib/idle.py in a console window, and report any
errors that you get.
--
nosy: +loewis
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9016
Martin v. Löwis mar...@v.loewis.de added the comment:
* I'd prefer if the crypto API didn't become OpenSSL specific (like the
SSL one is), which would theoretically allow switching in other crypto
provider(s).
I agree in theory, although I'm not sure how important this is likely
Martin v. Löwis mar...@v.loewis.de added the comment:
Does anyone know what other compilers use signed chars?
Most of them do, including gcc, on most platforms. unsigned char is really the
uncommon case.
The patch is incorrect; Py_CHARMASK is correct as it stands. It is *not* the
objective
Changes by Martin v. Löwis mar...@v.loewis.de:
--
title: Use locale encoding to decode sys.argv, not the file system encoding -
Use locale encoding to encode command line arguments (subprocess, os.exec*(),
etc.)
___
Python tracker rep
Martin v. Löwis mar...@v.loewis.de added the comment:
I'm still -1, failing to see the problem that is solved.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8775
Martin v. Löwis mar...@v.loewis.de added the comment:
Py_CHARMASK should return a non-negative integer.
And it does, also on AIX. Do we have proof to the contrary?
tokenizer.c:tok_get around line 1368:
while (Py_ISALNUM(c) || c == '_') {
c = tok_nextc(tok
Martin v. Löwis mar...@v.loewis.de added the comment:
What srid seems to be saying is that chars are unsigned on AIX, and
therefore Py_CHARMASK() returns -1. Hence his patch proposal.
Ah, ok. I misread some of the messages (and got confused by msg108125,
which seems to suggest that chars
Martin v. Löwis mar...@v.loewis.de added the comment:
Indeed. I think Py_ISALNUM() should check for EOF, to be consistent
with the C isalnum(int c).
Ah, that sounds fine.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org
Martin v. Löwis mar...@v.loewis.de added the comment:
You will need to delete TCL_LIBRARY and TK_LIBRARY in your environment settings.
--
nosy: +loewis
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9039
Martin v. Löwis mar...@v.loewis.de added the comment:
stable is also meant to mean typically passes test suite without errors. I
don't think OSX meets this criterion.
--
nosy: +loewis
___
Python tracker rep...@bugs.python.org
http://bugs.python.org
Martin v. Löwis mar...@v.loewis.de added the comment:
Here is a (untested) work-around that won't require undefining
_DARWIN_C_SOURCE: After all includes, say
#ifdef __APPLE__
int posix_getgroups(int, gid_t []) __asm(_getgroups);
#define getgroups posix_getgroups
#endif
This should cause
Martin v. Löwis mar...@v.loewis.de added the comment:
Am 22.06.2010 12:40, schrieb Ronald Oussoren:
Ronald Oussorenronaldousso...@mac.com added the comment:
Then why bother providing binaries?
How is that related? There was no OSX build slave until very recently,
but binaries had been
Martin v. Löwis mar...@v.loewis.de added the comment:
Here's the result of doing what Martin asked (and then launching the
interpreter, to confirm that it's the 2.5.4 version that I installed
on Thursday just before submitting my original bug report).
C:\PYTHON25 is the first item
Martin v. Löwis mar...@v.loewis.de added the comment:
Bit of a chicken/egg issue here. Since we haven't had OS X buildbots
for very long, and the ones we do have represent odd configurations,
I think it's premature to say that the port *doesn't* pass the test
suite on a regular manner
Martin v. Löwis mar...@v.loewis.de added the comment:
I don't know how relevant this is to OS X, but on FreeBSD 6.3,
kern.ngroups (maximum number of groups a uid may belong to) defaults
to 16.
It probably is: sysctl kern.ngroups also gives 16 on OSX 10.6.4
(Darwin 10.4.0
Martin v. Löwis mar...@v.loewis.de added the comment:
Is is possible to get e-mail about changes of buildbot status? I'd be
interested in two sets of mail: any buildbot failures caused by my
checkins and state changes for the OSX buildbots.
Buildbot failure reports are sent to python
Martin v. Löwis mar...@v.loewis.de added the comment:
Has anyone done anything about fixing this issue?
AFAICT, nobody did.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8852
Martin v. Löwis mar...@v.loewis.de added the comment:
Is there anything I can do to get someone to do something about it? I
would have thought with a patch, it would not be hard for someone to
fix.
Sure. Unfortunately, the day has only 24 hours
Martin v. Löwis mar...@v.loewis.de added the comment:
Ats some point in the future when the setproctitle project
(http://code.google.com/p/py-setproctitle/source/list) has matured it
will be reconsidered, correct?
No. It will also be required that it's authors agree to contribute
Martin v. Löwis mar...@v.loewis.de added the comment:
This is not a bug. You didn't *nearly* reset Python to the state in which it
was before the import: the modules that got imported recursively still hang in
sys.modules.
Please accept that Python indeed does not support unloading modules
Martin v. Löwis mar...@v.loewis.de added the comment:
I appreciate your point. But do you know if anyone has it on their
TODO list?
It's on my todo list, but that still might mean I can only get to
it next year.
If not, is there anything I could do about it?
You could invoke the 5-for-one
Changes by Martin v. Löwis mar...@v.loewis.de:
--
resolution: - wont fix
status: pending - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1565525
Martin v. Löwis mar...@v.loewis.de added the comment:
I still don't understand the issue. You say that you want a traceback, but then
you say you don't want the objects in the traceback. So what *precisely* is it
that you want, and what is it that you don't want?
In any case, whatever
Martin v. Löwis mar...@v.loewis.de added the comment:
Martin (Ellison): What people are trying to say is that likely, nobody will be
working on this, and likely so for the next few years. So unless you volunteer
to provide a patch, I recommend to close the issue as won't fix. Unassigning
Martin v. Löwis mar...@v.loewis.de added the comment:
This is not a problem. Tools/msi is being used with Python 2.5 only.
--
nosy: +loewis
resolution: - wont fix
status: open - closed
versions: -Python 3.1, Python 3.2
___
Python tracker rep
Martin v. Löwis mar...@v.loewis.de added the comment:
Here is the problem: there is no module multiprocessing._multiprocessing;
_multiprocessing is a global module. However, multiprocessing/__init__.py
imports _multiprocessing, providing multiprocessing._multiprocessing as a valid
attribute
Martin v. Löwis mar...@v.loewis.de added the comment:
I agree with John: this paragraph is technically incorrect. See
http://msdn.microsoft.com/en-us/library/ms681914%28v=VS.85%29.aspx
for an official definition of the relevant terms.
I vaguely recall objecting to that text when it got added
Martin v. Löwis mar...@v.loewis.de added the comment:
Dave, can you please take a look?
--
assignee: - dmalcolm
nosy: +dmalcolm, loewis
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9163
Martin v. Löwis mar...@v.loewis.de added the comment:
I don't think ctypes supports acc; try gcc instead.
--
nosy: +loewis
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9175
Martin v. Löwis mar...@v.loewis.de added the comment:
Can you provide a patch?
--
nosy: +loewis
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9176
Martin v. Löwis mar...@v.loewis.de added the comment:
Closing the report as third-party bug, then. A compiler crash is most
definitely not a bug in Python.
--
nosy: +loewis
resolution: - invalid
status: open - closed
versions: +3rd party -Python 2.7
Martin v. Löwis mar...@v.loewis.de added the comment:
Unfortunately, I typically don't have time to consider the priority of issues.
However, in the specific case, I also fail to see the bug. Where does it say
that they are supposed to be deleted when the process is killed, and what
mechanism
Martin v. Löwis mar...@v.loewis.de added the comment:
I can't think of any way that you might be able to implement the behavior
being requested here.
Thanks for the confirmation; lowering the priority then.
It would, of course, be possible to improve quality by registering an atexit
Martin v. Löwis mar...@v.loewis.de added the comment:
I think if you change it stop considering non-BMP characters as printable,
somebody will complain. If you change it in any other way, somebody will
complain. Somebody will always complain - so you might as well leave things the
way
Martin v. Löwis mar...@v.loewis.de added the comment:
No, but we do need to make sure that the casual user does not
run into such issues by using the default compiler on a typical
Unix system with Python default settings.
I think there is no risk here. The casual Python user on an AMD64
Martin v. Löwis mar...@v.loewis.de added the comment:
I think anybody willing to invest the time could acquire the appropriate
knowledge, at least to determine whether it's still an issue (i.e. trying to
reproduce it). To fix it, one would then need to read the source code of
hostname
Martin v. Löwis mar...@v.loewis.de added the comment:
I would like to know what happened with hex_codec and what is the new py3 for
this.
If you had read this bug report, you'd know that the codec was removed
in Python 3. Use binascii.hexlify/binascii.unhexlify instead (as you
should in 2.x
701 - 800 of 4659 matches
Mail list logo