[Python-bugs-list] [ python-Bugs-702157 ] No documentation of static/dynamic python modules.

[SourceForge.net]

Bugs item #702157, was opened at 2003-03-12 13:23
Message generated for change (Comment added) made by loewis
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=702157&group_id=5470

Category: Documentation
Group: Python 2.2.2
>Status: Closed
>Resolution: Works For Me
Priority: 5
Submitted By: J.A. Schonekerl (jschonek2)
Assigned to: Nobody/Anonymous (nobody)
Summary: No documentation of static/dynamic python modules.

Initial Comment:
Hi,

This problem cost me very much time to solve:

After I build Python, all dynamic libraries got dynamically
linked into the Python interpreter (libraries like
zlib and tcl/tk stuff).

I coudn't find out why this is, I only want to load zlib.so
when I do a "import zlib" and not when I start Python.

And this is (I think) the difference between statically and
dynamically build Python libraries, but this isn't explaind
in a clear way.

You can configure the dynamic/static module beheviour in
the Modules/Setup file (afher you did a configure) with
the *shared* flag. 

The dinamic/static module behaviour should at least very
clear described in that file, this is not the case at
this moment.

Best regards,

Jan







----------------------------------------------------------------------

>Comment By: Martin v. Löwis (loewis)
Date: 2003-05-11 22:42

Message:
Logged In: YES 
user_id=21627

Closing this because of lack of feedback.

----------------------------------------------------------------------

Comment By: Martin v. Löwis (loewis)
Date: 2003-03-17 19:51

Message:
Logged In: YES 
user_id=21627

I cannot reproduce this. If I leave # *shared*, but enable
zlib in Modules/Setup, I get no file Modules/zlib.so, only
Modules/zlib.o. This is incorporated into python.

If I also leave zlib commented in Modules/Setup, zlib.so is
build through setup.py in build/lib-somewhere, *after*
python was linked.

Can you provide a complete build log?

----------------------------------------------------------------------

Comment By: J.A. Schonekerl (jschonek2)
Date: 2003-03-17 13:02

Message:
Logged In: YES 
user_id=732192

Hi,

When I build python with zlib and the commented shared flag
"#*shared*". then zlib.so is included in ./python (checked
with ldd ./python).

When I build python with zlib and the  *shared* flag commented
out then is zlib.so not part of the ./python program.

The question is now: is this the difference between shared and
static modules?

or

do I have so weird problem?

----------------------------------------------------------------------

Comment By: Martin v. Löwis (loewis)
Date: 2003-03-15 14:29

Message:
Logged In: YES 
user_id=21627

What do you mean when you say "all dynamic libraries got
dynamically linked into the Python interpreter"? If it means
what I understand it means (i.e. all libraries are passed to
the ld command creating the python binary), then this is not
supposed to happen.

Can you provide a make log to demonstrate this more clearly?

----------------------------------------------------------------------

Comment By: J.A. Schonekerl (jschonek2)
Date: 2003-03-13 14:05

Message:
Logged In: YES 
user_id=732192

Uuuh when I say "python library" I mean a "python module"

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=702157&group_id=5470