Stéphane Wirtel added the comment:
Hi Ned,
For the first point, maybe close this issue and open a new bug for the second.
What do you think?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17095
Stéphane Wirtel added the comment:
Hi Ned,
What are the news for this issue?
--
nosy: +matrixise
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17095
___
Ned Deily added the comment:
Stéphane, as I understand it, this issue covers two problems:
(1) Building and installing shared modules using Modules/Setup was broken for
current Python 3 releases;
(2) Using those shared modules when running Python from a build directory
(rather than from a
Changes by Stefan Krah stefan-use...@bytereef.org:
--
nosy: -skrah
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17095
___
___
Python-bugs-list
Roundup Robot added the comment:
New changeset 781454f792c4 by Ned Deily in branch '3.4':
Issue #17095: Temporarily revert getpath.c change that added the Modules
https://hg.python.org/cpython/rev/781454f792c4
New changeset d3939f602e1f by Ned Deily in branch 'default':
Issue #17095: merge from
Changes by Ned Deily n...@acm.org:
--
priority: release blocker - normal
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17095
___
___
Ned Deily added the comment:
Clearly this breaks running from the build directory for various modules when
their optional C extension module build fails. I'll either change the Setup
shared builds to use a build directory or revert the path changes prior to the
upcoming 3.4.2.
--
Changes by John Malmberg wb8...@gmail.com:
--
nosy: +John.Malmberg
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17095
___
___
Python-bugs-list
Changes by Arfrever Frehtes Taifersar Arahesis arfrever@gmail.com:
--
nosy: +Arfrever
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17095
___
STINNER Victor added the comment:
I reopen the issue because these changes broke the decimal module when the
_decimal module is missing: see the issue #22285.
Martin von Loewis proposed to build modules in the build directory, not in the
Modules directory directly:
Changes by STINNER Victor victor.stin...@gmail.com:
--
nosy: +loewis, skrah
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17095
___
___
Roundup Robot added the comment:
New changeset 6c468df214dc by Ned Deily in branch '3.4':
Issue #17095: Fix Modules/Setup *shared* support.
http://hg.python.org/cpython/rev/6c468df214dc
New changeset 227ce85bdbe0 by Ned Deily in branch 'default':
Issue #17095: Fix Modules/Setup *shared*
Ned Deily added the comment:
Committed for release in 3.4.2 and 3.5.0.
--
resolution: - fixed
stage: patch review - resolved
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17095
Ned Deily added the comment:
Your original patch LGTM. However, since it was written, Setup *shared*
support became even more broken due to changes in Makefile macros. Attached is
an updated patch. I've never tried customizing Setup before so I don't have a
lot of confidence that it now
Changes by Georg Brandl ge...@python.org:
--
versions: -Python 3.2
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17095
___
___
Python-bugs-list
New submission from Thomas Wouters:
At some point (probably in 3.2) the support for shared modules built using
Modules/Setup was broken, for two reasons:
- Python no longer considers 'foomodule.so' when looking for a module called
'foo', but Modules/makesetup still appends 'module.so' for a
16 matches
Mail list logo
