Changes by Matthias Klose :
--
nosy: +twouters
___
Python tracker
<http://bugs.python.org/issue21274>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Matthias Klose :
--
nosy: +twouters
___
Python tracker
<http://bugs.python.org/issue21275>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Matthias Klose :
--
nosy: +twouters
___
Python tracker
<http://bugs.python.org/issue21276>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Matthias Klose :
--
nosy: +twouters
___
Python tracker
<http://bugs.python.org/issue21277>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Matthias Klose:
this refactors the curses configure checks, and fixes the build with ncursesw.
In it's current form the curses feature checks are run without the additional
include path which leads to wrong results if the only the nurses headers are
inst
Changes by Matthias Klose :
--
versions: +Python 2.7
___
Python tracker
<http://bugs.python.org/issue21285>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Matthias Klose :
--
nosy: +twouters
___
Python tracker
<http://bugs.python.org/issue21285>
___
___
Python-bugs-list mailing list
Unsubscribe:
Matthias Klose added the comment:
looks like with this change the curses extension isn't built anymore on Solaris.
--
nosy: +haypo
___
Python tracker
<http://bugs.python.org/is
Changes by Matthias Klose :
--
title: refactor anfd fix curses configure checks -> refactor and fix curses
configure checks
___
Python tracker
<http://bugs.python.org/issu
Matthias Klose added the comment:
fixed
--
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue21275>
___
___
Pyth
Matthias Klose added the comment:
fixed
--
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue21274>
___
___
Pyth
Matthias Klose added the comment:
fixed
--
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue21276>
___
___
Pyth
Matthias Klose added the comment:
Victor pointer out the Solaris issue is unrelated. See #13552. Closing.
--
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.org/i
Matthias Klose added the comment:
seen this again in our autopkg tester
https://jenkins.qa.ubuntu.com/view/Utopic/view/AutoPkgTest/job/utopic-adt-python3.4/12/
however now I can't reproduce this locally, and the test succeeds during the
build.
--
status: pending -&
Matthias Klose added the comment:
what happens here:
PYTHONPATH=$(pwd) python3.4 -X faulthandler -S -m compileall
Skipping current directory
Listing '/home/packages/python/3.4/x'...
Compiling '/home/packages/python/3.4/x/foo.py'...
Listing '/usr/lib/python3.4/'.
Matthias Klose added the comment:
so the issue here is that -L -o is passed to the compiler, and -o is
interpreted as the library dir, and as an input file.
To robustify, change distutils/tests/support.py to not include empty directory
names.
To fix, change configure.ac (RUNPATH) not to
Changes by Matthias Klose :
--
stage: needs patch -> patch review
___
Python tracker
<http://bugs.python.org/issue17752>
___
___
Python-bugs-list mai
Matthias Klose added the comment:
yes, noted myself (too late), and informed Georg about it. Closing for now.
--
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.org/i
Matthias Klose added the comment:
adding unittest developers
--
nosy: +ezio.melotti, michael.foord
___
Python tracker
<http://bugs.python.org/issue21264>
___
___
Matthias Klose added the comment:
adding unittest developers
--
nosy: +ezio.melotti, michael.foord
___
Python tracker
<http://bugs.python.org/issue17756>
___
___
Matthias Klose added the comment:
sure, doing this. my follow-up question was if it is necessary to fix anything
else in unittest.
--
___
Python tracker
<http://bugs.python.org/issue17
Matthias Klose added the comment:
not yet closing, to see if there are some stream buffering issues in mock
--
___
Python tracker
<http://bugs.python.org/issue17
New submission from Matthias Klose:
==
FAIL: test_license_exists_at_url (test.test_site.ImportSideEffectTests)
--
Traceback (most recent call last):
File
Matthias Klose added the comment:
they are. assume you build the zlib and elementtree extensions as builtins,
then libs for an interpreter includes libz and libexpat, while they are not
needed for extensions.
--
___
Python tracker
<h
Matthias Klose added the comment:
see issue #1161914 for the original script.
> 2) Since we are Pythoneers, why write this script as a
> shell-script instead of a Python script? (sh may not even be
> available on Windows).
python-config is usally not used by python module builds,
Changes by Matthias Klose :
--
nosy: +georg.brandl, loewis
___
Python tracker
<http://bugs.python.org/issue16235>
___
___
Python-bugs-list mailing list
Unsub
Matthias Klose added the comment:
Am 07.11.2012 13:52, schrieb Ray Donnelly:
>
> Ray Donnelly added the comment:
>
>> is there a need for the built vs. installed prefix?
>> this is logic not found in the python implementation.
>> what is this supposed to do?
&
Matthias Klose added the comment:
looks fine, just one more minor issue: please use @LIBPL@ directly.
there's no feedback from others, so I think this should go in as the extra
script first, and not replace the original one immedi
Matthias Klose added the comment:
oh, the equivalent for
flags = ['-I' + sysconfig.get_path('include'),
'-I' + sysconfig.get_path('platinclude')]
is still missing. I know that both scripts versions are only run post-install,
but
Changes by Matthias Klose :
--
nosy: +doko
___
Python tracker
<http://bugs.python.org/issue16480>
___
___
Python-bugs-list mailing list
Unsubscribe:
Matthias Klose added the comment:
having the posix_prefix as the default in Debian is an oversight on my side. it
always should be posix_local. I'll fix this at least for 3.3 in current
development releases.
The rationale for this is that distutils based installs install by default into
Matthias Klose added the comment:
virtualenv for 2.7, when used with a Debian/Ubuntu system installation, should
only see site-packages. Same thing should be done for venv for 3.3 and up.
Even if needed patches will not go upstream, they are welcome
Matthias Klose added the comment:
fixed in experimental, pyvenv's are now handled the same way as
python-virtualenvs. closing the issue here.
--
resolution: -> works for me
status: open -> closed
___
Python tracker
<http://b
Changes by Matthias Klose :
--
nosy: +doko
___
Python tracker
<http://bugs.python.org/issue16828>
___
___
Python-bugs-list mailing list
Unsubscribe:
Matthias Klose added the comment:
looks fine to me.
--
___
Python tracker
<http://bugs.python.org/issue16828>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Matthias Klose:
On MultiArch systems, header files are split into /usr/include and
/usr/include/. Make sure that h2py finds all headers.
Currently the build of IN.py is broken, when running on such a system.
--
components: Build
files: ma-h2py.diff
keywords: patch
Matthias Klose added the comment:
> 2-CROSS-use-_PYTHON_PROJECT_BASE-in-distutils-sysconfig.patch
This looks ok to me, just factoring out some code and setting the project base.
Even if distutils is frozen, I'll apply this one, based on Eric's comment in
http://bugs.python.o
Matthias Klose added the comment:
and adding the pybuilddir to PYTHONPATH, so that _sysconfigdata.py is found if
it does exist.
$(shell test -f pybuilddir.txt && echo $(abs_builddir)/`cat pybuilddir.txt`:)
--
___
Python tracke
Changes by Matthias Klose :
--
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue15484>
___
___
Python-bugs-list mailing list
Unsubscri
Matthias Klose added the comment:
updated the comment, the fixes for the duplicate issues are checked in.
--
status: open -> closed
___
Python tracker
<http://bugs.python.org/issu
Matthias Klose added the comment:
the change to the configure script looks ok. however you could change the
README too.
It looks like the changes to the Makefile.pre.in are already applied.
--
nosy: +doko
___
Python tracker
<http://bugs.python.
Matthias Klose added the comment:
in 3.3 and later, the test defaults to no when cross-building. If gcc is used
for the cross build, then a compile test is used.
it is usually needed to provide some values in a CONFIG_SITE file. See autoconf
for the details.
closing the issue
Matthias Klose added the comment:
I don't think this one is still necessary. can it be closed?
--
nosy: +doko
___
Python tracker
<http://bugs.python.org/is
New submission from Matthias Klose:
currently regen calls the python interpreter for the host, not the build
machine. You can't directly use BUILD_FOR_PYTHON, because this one uses
./python explicitly, so use BUILDPYTHON instead.
I'd like to see this for 3.3 and
Matthias Klose added the comment:
about py3k-20121004-CROSS.tgz:
- committed 0001-CROSS-fix-typo-in-thread-AC_CACHE_VAL.patch
- 0002-CROSS-restore-graminit.-to-source-directory.patch
is this necessary? Assuming that you have correct time
stamps, this is something which usually is not
Matthias Klose added the comment:
some random comments about py3k-20121004-MINGW.patch:
- Modules/_ctypes/libffi_msvc/win32.S
Please can you get rid of libffi_msvc and use libffi?
afaics, libffi has support for mingw32.
- there seem to be chunks which are unrelated to mingw, like
Changes by Matthias Klose :
--
resolution: -> fixed
stage: -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.or
Matthias Klose added the comment:
so here is what I intend to commit.
- --help now does exit with 0 (same as the python script)
- removed the abi safety check (always compares the same
two strings)
- build the script for the build target, so that it can be
checked before installing it
Matthias Klose added the comment:
now committed, using stdin for sed.
--
resolution: -> fixed
stage: patch review -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.or
Matthias Klose added the comment:
now checked in the configure change. I think that the cross-build documentation
deserves an extra issue. Therefore now closing this issue.
--
resolution: -> fixed
stage: patch review -> committed/rejected
status: open -&g
Matthias Klose added the comment:
> IMHO, updating these patches to track the latest Python is a pointless goal.
sorry, no. it's the *only* way to get these patches upstream. The mingw patches
will never see the light of the 3.3 branch. So the best thing to do is to
actively su
Matthias Klose added the comment:
> However, we must go further and add that the patches *cannot* break any
> other native or cross-compilation, which - as I think Matthias is
> alluding to - is probably not the case with your patch. This issue is
> called "cross and native bu
Matthias Klose added the comment:
just saw the comment about .hgtouch in
http://bugs.python.org/issue15819#msg169484
attaching a patch for it here (as proposed on python-committers).
--
nosy: +doko
Added file: http://bugs.python.org/file28874/hgtouch.diff
New submission from Matthias Klose:
I would like to check in a backport of the cross build patches on Thu or Fri,
so that these can be checked for the upcoming 2.7.4 release. The backport was
made using the current state of the cross build support on the 3.3 branch.
The patch is tested with
Matthias Klose added the comment:
config.add and config.sub are needed for the AC_CANONICAL_HOST macro. the patch
includes these and the regenerated configure script.
--
___
Python tracker
<http://bugs.python.org/issue17
Matthias Klose added the comment:
now committed, watching the buildds
--
stage: -> committed/rejected
status: open -> pending
type: -> enhancement
___
Python tracker
<http://bugs.python.or
Matthias Klose added the comment:
I'm planning to update the tip to the next libffi release candidate once it's
released.
Once this is checked in, maybe revisit the extra copy for OS X; an ABI issue
with llvm/clang was identified in
http://sourceware.org/ml/libffi-discuss/2013/msg
Matthias Klose added the comment:
> Ray Donnelly added the comment:
> Next time there's a release of Python 3, I'll rebase my patches against that.
sorry, this is the wrong attitude, if you want mingw support to go upstream.
fetch tip/trunk, re-apply your patches,
Matthias Klose added the comment:
now closing/rejecting this issue. See
http://mail.python.org/pipermail/python-dev/2013-January/123774.html
for the discussion.
--
resolution: -> rejected
stage: patch review -> committed/rejected
status: open -&g
Matthias Klose added the comment:
See http://mail.python.org/pipermail/python-dev/2013-January/123774.html
for the discussion.
Not updating the patches for tip/trunk is the best way to keep them out of the
project.
--
___
Python tracker
<h
Matthias Klose added the comment:
now closing/rejecting this issue. See
http://mail.python.org/pipermail/python-dev/2013-January/123774.html
for the discussion.
--
nosy: +doko
___
Python tracker
<http://bugs.python.org/issue16
Changes by Matthias Klose :
--
resolution: -> rejected
stage: -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.or
Matthias Klose added the comment:
2.7, 3.3 and 3.4 now have AC_CANONICAL_HOST. So the correct compiler should be
picked up. please could somebody validate this? or are explicit --host and
--build options required for configure?
--
nosy: +doko
New submission from Matthias Klose:
issue for tracking the libffi-3.0.12 import. checked that builds on
x86_64-linux-gnu and arm-linux-gnueabihf do work.
still needs updating/checking the extra copies of:
- libffi_arm_wince
- libffi_msvc
- libffi_osx
--
components: Extension
Matthias Klose added the comment:
libffi-3.0.12 is now imported, tracked in issue #17192.
--
___
Python tracker
<http://bugs.python.org/issue17136>
___
___
Pytho
Changes by Matthias Klose :
--
nosy: +ronaldoussoren
___
Python tracker
<http://bugs.python.org/issue17192>
___
___
Python-bugs-list mailing list
Unsubscribe:
Matthias Klose added the comment:
should go into 2.7 as well.
--
nosy: +doko
versions: +Python 2.7
___
Python tracker
<http://bugs.python.org/issue19308>
___
___
Matthias Klose added the comment:
the patch in msg202343 is wrong, hardcoding lib64 on Debian/Ubuntu. At least
the configure check should check for lib64 as a directory and not a symlink,
and only then default to lib64.
two other issues with the patch:
- I would like to see any new OS
Matthias Klose added the comment:
I disagree about sys.implementation. It's useless and wrong for cross builds.
Please use sysconfig instead. What sysconfig is maybe missing is a set of
variables which you can rely on.
--
___
Python tracker
Matthias Klose added the comment:
my concern here is that platform.linux_distribution returns different values
for the tuple, wether os-release is found or the lsb config file is found. I
don't know about a good solution, however if the return value has different
values, that has
New submission from Matthias Klose:
using the only mpdecimal release (2.3):
building '_decimal' extension
creating
build/temp.linux-x86_64-3.3/scratch/packages/python/3.3/python3.3-3.3.3/Modules/_decimal
x86_64-linux-gnu-gcc -pthread -fPIC -D_FORTIFY_SOURCE=2 -Wno-unused-result
-
Matthias Klose added the comment:
also, there is no VCS repository and no ML archive for mpdecimal publically
available.
--
nosy: +skrah
___
Python tracker
<http://bugs.python.org/issue19
New submission from Matthias Klose:
the posix module has the statvfs call, but doesn't define any constants used as
parameters. add them.
--
components: Extension Modules
files: statvfs-f_flag-constants.diff
keywords: patch
messages: 204043
nosy: doko
priority: normal
severity: n
Changes by Matthias Klose :
--
stage: -> patch review
type: -> enhancement
___
Python tracker
<http://bugs.python.org/issue19736>
___
___
Python-bugs-list
Matthias Klose added the comment:
updated patch inlcluding the docs
--
Added file: http://bugs.python.org/file32821/statvfs.diff
___
Python tracker
<http://bugs.python.org/issue19
Matthias Klose added the comment:
Am 24.11.2013 18:42, schrieb Stefan Krah:
> _decimal should only be built against the upcoming mpdecimal-2.4.
is there a schedule for this version?
--
___
Python tracker
<http://bugs.python.org/issu
Matthias Klose added the comment:
2.4~rc1:
- configure.ac should call AC_CANONICAL_HOST, config,guess and
config.sub should be included.
- there are still symbols which exists only for 32/64 bit archs.
intended?
(arch=@64@)mpd_qsset_i64@Base 2.3
(arch=@64@)mpd_qsset_u64@Base 2.3
Matthias Klose added the comment:
Am 25.11.2013 12:42, schrieb Stefan Krah:
>
> Stefan Krah added the comment:
>
> Matthias Klose wrote:
>> 2.4~rc1:
>> - configure.ac should call AC_CANONICAL_HOST, config,guess and
>>config.sub should be included.
>
&g
Matthias Klose added the comment:
re-opening. the patch did break autopilot running with 2.7 on Ubuntu. I don't
yet understand what this patch is supposed to fix.
--
nosy: +doko
resolution: fixed ->
status: closed -> open
___
Python tra
Matthias Klose added the comment:
see https://launchpad.net/bugs/1255505
--
___
Python tracker
<http://bugs.python.org/issue19352>
___
___
Python-bugs-list mailin
Matthias Klose added the comment:
http://tracker.ceph.com/issues/8797 reports that the backport to 2.7 causes a
regression in ceph.
--
nosy: +benjamin.peterson, doko
status: closed -> open
___
Python tracker
<http://bugs.python.org/iss
Matthias Klose added the comment:
3.4.0 has this fixed. resolutions in http://bugs.python.org/issue16074 and
http://bugs.python.org/issue20517
--
nosy: +doko
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.p
New submission from Matthias Klose:
tracking the import of libffi 3.1
--
components: ctypes
messages: 225109
nosy: doko
priority: normal
severity: normal
status: open
title: update internal libffi copy to 3.1, introducing AArch64 and POWER ELF
ABIv2
versions: Python 3.4, Python 3.5
Matthias Klose added the comment:
this is fixed in the 3.4 branch (post 3.4.1) and on all active branches. you
should be able to use --with-system-libffi in your current environment (maybe
after running: apt-get build-dep python3.4.
--
resolution: -> fixed
status: open ->
New submission from Matthias Klose:
there are some tests failing when http_proxy and https_proxy is set and the
network resource is enabled. I didn't analyze things, but I assume there needs
some more fine-grained control about the network resource.
the log of such a run is attached.
Matthias Klose added the comment:
forgot: some tests fail as well with -uall,-network and configured proxies.
--
___
Python tracker
<http://bugs.python.org/issue22
New submission from Matthias Klose:
I'd like to update zlib in 2.7 to 1.2.8. zlib isn't used at all for posix
builds, because it requires a system installed zlib. However I don't know what
is is used for Windows and MacOSX. Please could somebody check?
My rationale for the upd
Changes by Matthias Klose :
--
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue22381>
___
___
Python-bugs-list
Matthias Klose added the comment:
causing #22523, still referencing _ssl.sslwrap.
--
nosy: +doko
___
Python tracker
<http://bugs.python.org/issue21308>
___
___
New submission from Matthias Klose:
the backport in issue #21308 caused this regression. _ssl.sslwrap is still
referenced in some files.
--
components: Library (Lib)
messages: 227896
nosy: alex, benjamin.peterson, christian.heimes, doko, dstufft,
giampaolo.rodola, janssen, pitrou
Matthias Klose added the comment:
forwarded from https://bugs.debian.org/762010
--
___
Python tracker
<http://bugs.python.org/issue22523>
___
___
Python-bug
Matthias Klose added the comment:
fixed in 2.7, 3.4 and 3.5
--
resolution: -> fixed
status: open -> closed
versions: +Python 2.7 -Python 3.3
___
Python tracker
<http://bugs.python.org/i
Matthias Klose added the comment:
fixed in 2.7, 3.4 and 3.5
--
resolution: -> fixed
status: open -> closed
versions: +Python 2.7, Python 3.5
___
Python tracker
<http://bugs.python.org/i
Matthias Klose added the comment:
no, it doesn't. at least when testing the installed python installation, it
just fails:
https://jenkins.qa.ubuntu.com/job/utopic-adt-python2.7/39/?
--
nosy: +doko
resolution: fixed ->
status: closed
Matthias Klose added the comment:
maybe, but then you should skip the test, or expect at least a MemoryError.
--
___
Python tracker
<http://bugs.python.org/issue22
Changes by Matthias Klose :
--
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue19736>
___
___
Python-bugs-list
New submission from Matthias Klose:
test_urllib2net is run even when the network resource is disabled, unlike
test_urllibnet:
run_tests.py -j 1 -w -uall,-network,-urlfetch
...
[349/380/6] test_urllib2net
Resource 'http://www.python.org/' is not available
Resource 'http://www.
Changes by Matthias Klose :
--
nosy: +zach.ware
___
Python tracker
<http://bugs.python.org/issue20070>
___
___
Python-bugs-list mailing list
Unsubscribe:
Matthias Klose added the comment:
this fixes it for me:
--- a/Lib/test/test_urllib2net.py Wed Dec 25 17:36:20 2013 +0200
+++ b/Lib/test/test_urllib2net.py Thu Dec 26 17:05:47 2013 +0100
@@ -14,6 +14,8 @@
except ImportError:
ssl = None
+support.requires("network")
Matthias Klose added the comment:
fixed
--
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue20070>
___
___
Python-bugs-list mai
401 - 500 of 827 matches
Mail list logo
