python-debconf, Byte compilation and other questions

[Tim Dijkstra <newsuser@famdijkstra.org>]

Hi,

I'm trying to create a package of a program that's written in
python (web2ldap). I think I already have it working OK, but having no
prior python experience I have a few questions. 
Oh, btw, I checked the archives, and found out that some of these issues
have been discussed already, but I couldn't find consensus on these
topics. 

1) Should I ship .py or .pyc or both in the package. Byte-compile at
install time? Ask user what to do? 
Ok, just saw a few other messages on this, my conclusion:
 Byte-compile at install time
But how do I force the .py to get re-bytecompiled when a newer python
becomes the default? With a depends python < X.Y? Seems a waste of band
with, to download a new package only for its postinst run...

2) I would like to use the debconf-module, but it seems there is no
python priority:required, so is this module worthless? 

3) The program is pure python code, so I guess it can be arch:all if I
ship only .py files, but are .pyc files also arch-independent?

If you don't feel like answering all these questions (you can do it
in any case), could you point me to a package that is packaged as all
python programs should? 

grts Tim