Monster python24.dll / stripping off asian codecs to separate package(s) ?

[Robert]

Indeed, it would. As I said before: if somebody defines a clear, fair
policy which finds agreement in the community, I'm willing to change the
current policy on what goes into python24.dll, and what is built
separately. Bonus points if the policy is accompanied with a patch.
The policy should not be static, i.e. it should also give a guideline
for modules introduced in the future.
At the moment, the policy is this: "everything that does not depend on
an external library should go into pythonXY.dll". As a result of this

reducing the big python24.dll is still a tangling issue: keeping up
with new python versions. creating an installer or copying files
around. unsecurty, if the compiler is error free ...
for me the big DLL size is the only reason to rebuild python. Guess
there are more people suffering from the doubled size of python24.dll
vs python23.dll

I guess there is no good mathematical policy. But maybe a practical one
(as pythons policy is practicability - not to be a LISP): the size of
the libraries. 'd perfectly happy if the asian codecs are out.

A practical policy: respect size + usage frequency :

For future independent libs: Check their size. If they they are
monsters, check if the lib is used in more than 80% of applications. if
not, keep monster libs sparately, as they blow up installers and memory
usage.

Robert

 

[Robert]

A bugfix release 2.3.6 would also be a good idea.

I suffered at once from 2 severe errors pending in 2.3 (fixed in 2.4)
when going back to 2.3.5 (because of the monster python24.dll issue):

* httplib.HTTP(x)Connect inserts still double Content-length headers
whichs breaks on many servers.

* _ssl.pyd has not the recent fixes.

Robert