RFC: python-base, debconf and py/pyc files

Hi, currently, our Python packages mostly ship .py files and compile them into .pyc files at run time in order to save space in the debs. There's no reason, though, to keep the .py files on machines that only deploy software[1] I wonder if I should debconf-ify python-base and add an debconf opti

Re: RFC: python-base, debconf and py/pyc files

I think this sounds good. Then users who don't want to use the extra disk space don't have to. There is another tradeoff though. I compared the size of several .py and the corresponding .pyc files from the standard library and noticed that the .pyc file is a little bit larger. If the user li