Matthias Klose added the comment:
your current repo doesn't create and install the .so symlink, and thus won't be
used for linking.
Also the sphinx docs are missing, which were included in 2.3.
--
___
Python tracker
<http://bu
Matthias Klose added the comment:
Victor, what should be returned if the code name is not set? None, empty
string, or the description field of the lsb-release file?
--
___
Python tracker
<http://bugs.python.org/issue1
Matthias Klose added the comment:
sure, then please let's deprecate that for 3.4, and remove in 3.5.
/etc/os-release introduce the next set of different names.
--
___
Python tracker
<http://bugs.python.org/i
Matthias Klose added the comment:
I like this, and I'm doing this in the Debian/Ubuntu packaging anyway. But I
would like to see some check script which maybe can be run before a release,
that points out regressions or wrong permissions for newly introduced files.
--
nosy:
New submission from Matthias Klose:
shutil imports distutils in _call_external_zip just for the calling of an
external command. This should be done using subprocess these days.
--
components: Library (Lib)
messages: 212007
nosy: doko
priority: normal
severity: normal
stage: needs
Matthias Klose added the comment:
no, I requested that you propose a patch. And the question why you need to
include Python.h everywhere where it could do harm is unanswered too.
--
nosy: +doko
___
Python tracker
<http://bugs.python.org/issue20
Matthias Klose added the comment:
this looks safe from my point of view.
However the real problem is that you unconditionally add a runtime path for a
standard system path. I think the better way to fix this is not to pass the -L
and -R arguments at all if the library is found in a system
Matthias Klose added the comment:
both patches assume that everybody uses lib64 for 64bit libs, which is
not true for Debian/Ubuntu. Even the FHS doesn't mandate the use of lib64.
--
nosy: +doko
___
Python tracker
<http://bugs.py
Matthias Klose added the comment:
fixed in 2.6, 2.7, 3.1, 3.2
--
nosy: +doko
resolution: -> fixed
status: open -> closed
versions: +Python 3.2
___
Python tracker
<http://bugs.python.org/
New submission from Matthias Klose :
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41443
should be imported.
I'm checking this in on the 2.6 branch for the upcoming 2.6.3 release.
--
assignee: theller
components: ctypes
messages: 93047
nosy: doko, theller
severity: normal
status:
Changes by Matthias Klose :
--
nosy: +doko
___
Python tracker
<http://bugs.python.org/issue7111>
___
___
Python-bugs-list mailing list
Unsubscribe:
Matthias Klose added the comment:
This change shows a regression (https://bugs.launchpad.net/bugs/449734),
the setup.py file might not be correct, but it did work before this
change (with plain distutils). Quoting from the report:
Set setup.py file looks like this:
setup(name='update-ma
New submission from Matthias Klose :
Got an user report about setup.py install not honoring PYTHONUSERBASE.
Is this by design? If not, the attached patch seems to implement this
functionality.
--
assignee: tarek
components: Distutils
files: userbase.diff
keywords: patch, patch
messages
New submission from Matthias Klose :
% /sbin/ldconfig -p | grep GL
libGLU.so.1 (libc6) => /usr/lib/libGLU.so.1
libGLEW.so.1.5 (libc6) => /usr/lib/libGLEW.so.1.5
libGL.so.1 (libc6, Système d'exploitation ABI : Linux 2.4.20) =>
/usr/lib/libGL.so.1
the regexp fails
Matthias Klose added the comment:
msg94560 should read "backported to the 2.6 branch". can we close the
report?
--
nosy: +doko
___
Python tracker
<http://bugs.python.
New submission from Matthias Klose :
no change in behaviour in 2.6
the mailbox module in python 2.5 cannot modify mboxes in read-only
directories, e.g. the system mail spool. This is because
mailbox._singlefileMailbox.flush() tries to write the modified mailbox
to a temporary file and then
New submission from Matthias Klose :
[forwarded from http://bugs.debian.org/451733]
the mailbox._singlefileMailbox class is not safe with concurrent access,
because mailbox._singlefileMailbox.flush() replaces the underlying file
with a new copy by constructing a temporary file and then renaming
Changes by Matthias Klose :
Added file: http://bugs.python.org/file15364/mailbox-race.py
___
Python tracker
<http://bugs.python.org/issue7360>
___
___
Python-bugs-list m
Matthias Klose added the comment:
$ LANG=C /sbin/ldconfig -p | fgrep GL
libGLU.so.1 (libc6) => /usr/lib/libGLU.so.1
libGLEW.so.1.5 (libc6) => /usr/lib/libGLEW.so.1.5
libGL.so.1 (libc6, OS ABI: Linux 2.4.20) => /usr/lib/l
Matthias Klose added the comment:
this patch looks wrong, as it only works with libffi >= 3.0 (the standalone
libffi releases, which introduces the pkg-config stuff).
--
nosy: +doko
___
Python tracker
<http://bugs.python.org/iss
New submission from Matthias Klose :
in 3.x the _dbm extension can only be built with gdbm as the backend
library. gdbm is licensed under the GPL, so some people/projects like
Debian may have objections to build _dbm with the gdbm backend. It gets
difficult to determine, which code then uses
New submission from Matthias Klose :
| File "build/temp.linux-mips-2.6/libffi/fficonfig.py", line 32, in
| ffi_sources += ffi_platforms['MIPS']
| KeyError: 'MIPS'
however the fficonfig.py file has only MIPS_LINUX and MIPS_IRIX keys.
--
assign
Matthias Klose added the comment:
MAL, please can we add zooko's patch in some form? The current
implementation assumes an implementation, which doesn't exist on all
platforms, and just dividing linux distributions in "unsupported" and
"supported" seems to b
Changes by Matthias Klose :
___
Python tracker
<http://bugs.python.org/issue1322>
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/o
Matthias Klose added the comment:
These are the symbols on the trunk (20090328). There are *very* general
names as well. How should this be resolved? Introduce macros for the old
names, or just rename these?
module_methods probably could be static.
AllocFunctionCallback
ArrayType_Type
New submission from Matthias Klose :
pyexpat.c defines the global symbol template_string polluting the global
namespace, which isn't used in the module. Is it ok to remove this
definition altogether?
--
messages: 84333
nosy: doko
severity: normal
status: open
title: pyexpat de
New submission from Matthias Klose :
There are four global symbols in libpython, which have are globally
defined, and don't have a Py prefix. Would it be possible to define
those with a _Py prefix instead?
--
messages: 84334
nosy: doko
severity: normal
status: open
title: global sy
New submission from Matthias Klose :
encodefuncs is only used locally. ok to make this variable static?
--
messages: 84335
nosy: doko
severity: normal
status: open
title: Modules/_textio.c defines global symbol encodefuncs
___
Python tracker
<h
Matthias Klose added the comment:
> I'm sure it does work, but what is the point of linking statically
> to libpython.a but then having other dependencies, for example on
> lib-dynload/time.so? Why not just link to libpython2.5.so in the
> first place?
speed. Using a python
Matthias Klose added the comment:
sorry, forgot to add these ...
_add_one_to_index_C
_add_one_to_index_F
asdl_int_seq_new
asdl_seq_new
--
___
Python tracker
<http://bugs.python.org/issue5
Matthias Klose added the comment:
fixed for 2.7, 2.6, 3.1
--
assignee: -> doko
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.o
New submission from Matthias Klose :
[forwarded from http://bugs.debian.org/519454]
"""
As of now, warnings.py provides only re.I flag to re.compile on
warnings.py:160. Recent python-numpy issues way too many warnings, I
was trying to filter them out using warnings.filterwa
New submission from Matthias Klose :
GNU tar now supports lzma compression as a compression method. Please
consider adding lzma support to the tarfile module (either by using the
external lzma program or by adding a lzma extension to the standard
library).
lzma extension at http
New submission from Matthias Klose :
[forwarded from http://bugs.debian.org/411524]
"""
If you feed the output of pydoc -w [some module] to the w3 validator, it
complains about two issues:
firstly, the doctype is wrong. It should be:
not
in
the head
wo
Matthias Klose added the comment:
committed these in r71229 and r71271. I'm not yet closing the report.
tim_one, I will conditionalize these, but I'm unsure if these should be
conditionalized on compilers which are known not to optimize, or if it
should be just conditionalized on gc
Matthias Klose added the comment:
here is an updated patch, adding a new configure option
--with-dbmliborder, and checking the config args in setup.py.
this is the same approach as taken with the --with-system-libffi option.
--
nosy: +doko
Added file: http://bugs.python.org/file13645
Matthias Klose added the comment:
fixed on the 3.0 and 3.1 branches
--
assignee: -> doko
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.o
Matthias Klose added the comment:
is there any chance for inclusion in 3.1?
--
nosy: +doko
___
Python tracker
<http://bugs.python.org/issue3783>
___
___
Pytho
Matthias Klose added the comment:
I'm removing the db4.6 check instead. This was useful when building the
_bsddb3 extension, where threading tests would fail on these
architectures. It's not necessary for building the _dbm extension.
--
Matthias Klose added the comment:
> Ok. Just make sure "make clean; make" works.
done. the "make clean" was missing before.
--
resolution: -> fixed
status: open -> closed
___
Python tracker
<
Matthias Klose added the comment:
checked in my patch as rev72107 on the trunk. Will apply it for py3k
tomorrow.
--
___
Python tracker
<http://bugs.python.org/issue4
Matthias Klose added the comment:
applied on the py3k branch as well
--
resolution: -> accepted
status: open -> closed
___
Python tracker
<http://bugs.python.org/
Matthias Klose added the comment:
fixed in rev 73503
--
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.org/
Matthias Klose added the comment:
Per, on 2010-03-17, I asked you via email:
"I was looking at
http://bugs.python.org/issue5689
http://bugs.python.org/issue6715
and Martin's comments about the licensing of the bindings; is there a special
reason for the lgpl3 license of th
Changes by Matthias Klose :
--
nosy: +doko
___
Python tracker
<http://bugs.python.org/issue6715>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Matthias Klose :
string exceptions still used in a couple of places:
Tools/msi/msi.py:354
Tools/msi/msi.py:368
Tools/msi/msilib.py:238
--
components: Demos and Tools
messages: 108900
nosy: doko
priority: normal
severity: normal
status: open
title: Tools/msi still
Matthias Klose added the comment:
this breaks the build if the time and datetime extensions are built statically
into the python interpreter.
The build fails with a link error; adding the _time extension to
Modules/Setup.dist
@@ -160,6 +160,7 @@
#cmath cmathmodule.c _math.c # -lm # complex
Changes by Matthias Klose :
--
resolution: fixed ->
___
Python tracker
<http://bugs.python.org/issue9012>
___
___
Python-bugs-list mailing list
Unsubscri
Matthias Klose added the comment:
please find attached a patch to build as a statically linked extension,
registering the empty _time module.
--
Added file: http://bugs.python.org/file17853/time.diff
___
Python tracker
<http://bugs.python.
Matthias Klose added the comment:
doesn't work:
ranlib libpython3.2.a
Modules/_time.o: In function `_PyTime_DoubleToTimet':
/scratch/packages/python/3.2/python3.2-3.2~~20100704/build-shared/../Modules/_time.c:11:
multiple definition of `_PyTime_DoubleToTimet'
Modules/_time.o:/s
Matthias Klose added the comment:
yes, same issue with math/cmath.
--
___
Python tracker
<http://bugs.python.org/issue9012>
___
___
Python-bugs-list mailin
New submission from Matthias Klose :
[forwarded from https://launchpad.net/bugs/597763]
seen with all version, built with Tcl8.5
To reproduce the bug, use the following class:
class x(object):
TEST = "hello"
THE_MAXIMUM = 55
def __init__(self, a, b):
self.a = 3
self.b = &
Matthias Klose added the comment:
> what version of gcc is being used by this buildslave
you already found out, but it's mentioned at the top of the test stdio. I'll
update the compiler and recheck.
--
___
Python tracker
<http:/
Matthias Klose added the comment:
I updated the compiler on the buildbot to trunk 20100709, and your reduced
testcase is fixed. will update the gcc-snapshot package in maverick later.
--
resolution: -> fixed
status: open -> closed
___
Matthias Klose added the comment:
shouldn't `initialised_setupterm' be tested instead?
--
nosy: +doko
___
Python tracker
<http://bugs.python.
Matthias Klose added the comment:
see https://lists.ubuntu.com/archives/ubuntu-devel/2010-July/031010.html
--
___
Python tracker
<http://bugs.python.org/issue9
Matthias Klose added the comment:
committed in r83306 (2.7) and r83307 (3.2); verified that the behaviour in
offlineimap (reported in http://bugs.debian.org/586433 is fixed).
will apply it to 2.6 and 3.1 after a few days.
--
resolution: -> fixed
status: open -> pending
ve
Matthias Klose added the comment:
IMO using lsb_release is not an option, because it can take some time to
complete. So maybe it's better for the Ubuntu change to guard the check with
the existance of /etc/debian_version.
Please could you attach a Mandriva lsb-release
Matthias Klose added the comment:
This approach will not work with a "multiarch" enabled environment, and break
cross builds on Debian and Ubuntu.
Afaics, the proposal assumes that the python executable for the target
architecture is installed (which it is not for the multiarch c
Matthias Klose added the comment:
> * The sysconfigdata file name was terminated with a dangling
> underscore when 'multiarch' is not defined.
That only solves part of the problem in that the kernel/os version gets encoded
as well, e.g. gnukfreebsd9, gnukfreebsd10, which i
Matthias Klose added the comment:
again, I don't think relying on a specific target path for a cross target is a
good idea. and now deciding that the last possibility to use a target id to
identify is better is internal doesn't make it better. I'd appreciate if we
could sit
Matthias Klose added the comment:
> An idea is renaming it to something like target_architecture
> to make things clearer
Yes, that was my intent, and I think it is the right solution. using
$(MACHDEP)_$(MULTIARCH) in the sysconfigdata name and probably in other places
was not a goo
Matthias Klose added the comment:
> Hum, you still need to provide the native python interpreter
> with the _path_ to the -python-config executable that
> can be anywhere on the file system
No, it's found in the same path. No contradiction.
> So I suggest we start with this
Matthias Klose added the comment:
the upstream ncurses has the ncursesw subdirinclude name, so you apparently can
assume that this directory name is fixed *iff* it exists, however the ncursesw
installation can be found in /include instead. Can your changes cope
with that?
second issue is
Matthias Klose added the comment:
this assumption is wrong for the multiarch case.
--
___
Python tracker
<http://bugs.python.org/issue20211>
___
___
Python-bug
Matthias Klose added the comment:
> The only change that is needed here is to not include
> /usr/include/ncursesw in setup.py when cross compiling
no, this is a very wrong simplification. Both gcc and clang offer a method to
search for header files and libraries in a target specific lo
Matthias Klose added the comment:
https://trac.sagemath.org/ticket/22037 reports about another regression.
--
nosy: +doko
___
Python tracker
<http://bugs.python.org/issue5
Matthias Klose added the comment:
Fyi, Debian's 1.1.0c is fixed, so please don't blacklist this version in
general.
--
nosy: +doko
___
Python tracker
<http://bugs.python.o
New submission from Matthias Klose:
These are the changes updating zlib from 1.2.8 to 1.2.10. It is only used when
building without a system zlib. The new release includes fixes for security
issues CVE-2016-9840, CVE-2016-9841, CVE-2016-9842, CVE-2016-9843.
Intending to update all active
Matthias Klose added the comment:
ok, will wait with the commits until after the releases.
--
___
Python tracker
<http://bugs.python.org/issue29169>
___
___
Pytho
Matthias Klose added the comment:
the idea is that we load a different _sysconfigdata module when we are cross
building packages. So we don't know the name in advance. An ugly alternative
would be a big if statement with conditional imports for all known cross build
targets. Not su
Matthias Klose added the comment:
I don't think we need a PEP for this, however I would like to name the new
macro libsubdir, or sublibdir, to make it clear it's just the libdir component.
Or make the value absolute, like it already is
Matthias Klose added the comment:
plus the update to 1.2.11
--
title: update zlib to 1.2.10 -> update zlib to 1.2.11
Added file: http://bugs.python.org/file46464/zlib-1.2.11.diff
___
Python tracker
<http://bugs.python.org/issu
Matthias Klose added the comment:
now updated all active branches to 1.2.11
--
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.org/i
Matthias Klose added the comment:
I don't see the point of having an option to do that. Will patches for third
party projects be submitted as well, to not install the test suite? Or will pip
gain such a feature? Note that removing the test suite completely, you'll make
the test
Matthias Klose added the comment:
even for the window builds, I don't see any use of these icons for any build. I
filed https://github.com/python/pythondotorg/issues/945 to make these files
available as downloadable resources. However even if these are not accepted
there, I think we s
Changes by Matthias Klose :
--
nosy: +ned.deily, steve.dower
___
Python tracker
<http://bugs.python.org/issue17500>
___
___
Python-bugs-list mailing list
Unsub
New submission from Matthias Klose:
Some python extensions provide/rely on support libraries which are shipped in
addition to the extension module, and which depend on the Python ABI (version
and ABI flags). talloc is such an example, and it currently uses the SOABI as
the symbol version for
Changes by Matthias Klose :
--
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue25151>
___
___
Python-bugs-list
Matthias Klose added the comment:
The current Debian packages show this error message:
$ python3 -m venv /tmp/foobar
The virtual environment was not created successfully because ensurepip is not
available. On Debian/Ubuntu systems, you need to install the python3-venv
package using the
Changes by Matthias Klose :
--
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue26884>
___
___
Python-bugs-list
Matthias Klose added the comment:
maybe we don't need that. you already can do:
import sys
'%s-%d%d%s' % (sys.implementation.name, sys.version_info[0],
sys.version_info[1], sys.abiflags)
'cpython-35m'
--
___
Python tracker
Matthias Klose added the comment:
attaching an updated patch. besides renaming of the platform directory, the
following changes are made:
- it makes the name of the internal _sysconfigdata module dependent
on the abiflags
- it moves the _sysconfigdata module into the platform directory
Changes by Matthias Klose :
--
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue21272>
___
___
Python-bugs-list
Matthias Klose added the comment:
The 0002-* patches look fine, however the 0001-* patches are wrong if you are
in a Multi-Arch environment, where you can find valid headers in /usr/include.
From my point of view, the set of include and header directories should be
directly initialized from
Matthias Klose added the comment:
fyi, this came up again at the 2016 Language Summit, the request here was to
provide some minimal packages which are just enough to run a cloud image (the
cloud-init package requires a somehow minimal python
Changes by Matthias Klose :
--
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue21277>
___
___
Python-bugs-list
Matthias Klose added the comment:
I'm unable to reproduce this with the 2.7 branch 20160603.
--
___
Python tracker
<http://bugs.python.org/issue27052>
___
___
Changes by Matthias Klose :
--
resolution: -> works for me
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue27052>
___
___
Pyth
Matthias Klose added the comment:
(checked with the recent packages in Debian unstable and Ubuntu yakkety)
--
___
Python tracker
<http://bugs.python.org/issue27
Matthias Klose added the comment:
sorry, I don't understand your last comment.
--
___
Python tracker
<http://bugs.python.org/issue27101>
___
___
Python-bugs-l
Matthias Klose added the comment:
On 07.06.2016 16:47, Christian Heimes wrote:
>
> Christian Heimes added the comment:
>
> PSRT VETO!
>
> In the light of the upcoming release 3.5.2 I'm now putting on my PSRT hat
> (Python Security Response Team) and proclaim
Matthias Klose added the comment:
removed the PC/icons directory.
--
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.org/i
Matthias Klose added the comment:
CristiFati, please could you check if the libffi patch is still needed with the
current upstream libffi?
See https://github.com/libffi/libffi
--
___
Python tracker
<http://bugs.python.org/issue25
Matthias Klose added the comment:
ubuntu doesn't do anything crazy, but just disables oldish, deprecated und
probably now unsecure ssl protocols. This is done by other vendors as well.
From my point of of view this skip_if_ubuntu stuff should be replaced by proper
feature tests. I
Matthias Klose added the comment:
Description: properly handle Ubuntu's openssl having OP_NO_SSLv3 forced on by
default
Author: Marc Deslauriers
Forwarded: yes, http://bugs.python.org/issue25724
Index: b/Lib/test/test_s
New submission from Matthias Klose:
pydoc: prefer the pager command in favor of the specifc less command. the pager
command on Debian/Ubuntu systems is an alternative which is provided by
specific pagers like less or more.
References:
http://unix.stackexchange.com/questions/5383/which-systems
Matthias Klose added the comment:
adding MANPAGER, with the simpler logic.
--
nosy: +doko
title: Add PYDOCPAGER envvar to specify pager for pydoc -> Add MANPAGER envvar
to specify pager for pydoc
___
Python tracker
<http://bugs.python.org/iss
Matthias Klose added the comment:
fixed for 3.6.0a3
--
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue8637>
___
__
Matthias Klose added the comment:
now checked in, after 3.6.0a2, to watch behaviour on different platforms. Still
needs doc updates.
--
___
Python tracker
<http://bugs.python.org/issue23
501 - 600 of 827 matches
Mail list logo