[Antoine Pitrou, 2010-09-13]
I meant how these decisions are implemented. Is there a configure
switch (there doesn't seem to be)? Does it require patching Python?
Ah, no. Standard configure switches are used. Debian (inherited by Ubuntu)
has a post-installation script for Python
On Mon, 13 Sep 2010 16:18:44 +0200 (CEST)
barry.warsaw python-check...@python.org wrote:
-For an arbitrary package `foo`, you would see these files when the
+For an arbitrary package `foo`, you might see these files when the
distribution package was installed::
-
On Sep 13, 2010, at 04:36 PM, Antoine Pitrou wrote:
On Mon, 13 Sep 2010 16:18:44 +0200 (CEST)
barry.warsaw python-check...@python.org wrote:
-For an arbitrary package `foo`, you would see these files when the
+For an arbitrary package `foo`, you might see these files when the
distribution
On Mon, 13 Sep 2010 10:55:16 -0400
Barry Warsaw ba...@python.org wrote:
On Sep 13, 2010, at 04:36 PM, Antoine Pitrou wrote:
On Mon, 13 Sep 2010 16:18:44 +0200 (CEST)
barry.warsaw python-check...@python.org wrote:
-For an arbitrary package `foo`, you would see these files when the
+For
On Sep 13, 2010, at 05:04 PM, Antoine Pitrou wrote:
On Mon, 13 Sep 2010 10:55:16 -0400
Barry Warsaw ba...@python.org wrote:
On Sep 13, 2010, at 04:36 PM, Antoine Pitrou wrote:
-/usr/share/pyshared/foo.cpython-32m.so
-/usr/share/pyshared/foo.cpython-33m.so
+
I meant how these decisions are implemented. Is there a configure
switch (there doesn't seem to be)? Does it require patching Python?
Ah, no. Standard configure switches are used. Debian (inherited by Ubuntu)
has a post-installation script for Python packages which create the .py
Am 13.09.2010 17:36, schrieb Antoine Pitrou:
I meant how these decisions are implemented. Is there a configure
switch (there doesn't seem to be)? Does it require patching Python?
Ah, no. Standard configure switches are used. Debian (inherited by Ubuntu)
has a post-installation script for
