[meego-packaging] Guidelines for dealing with Python byte code files

[Jian-feng Ding]

For python module packages in MeeGo, all the byte code, *.pyc and *.pyo, will
be included in final rpms.
Actually this problem is not spectacle related one, just a rpm building system
setting instead.
So we need to care about it, just follow the MeeGo building system's default.

On Wed, Nov 17, 2010 at 10:34:52PM +0800, Pertti Kellomäki wrote:
> I remember some discussion in the mailing list about how to deal with 
> Python byte code files, but I could not find anything. What are the 
> guidelines for dealing with .pyc files? Should we just package them and 
> be happy, or should be tell the build system to ignore them? If the 
> option is to ignore, what is the spectacle way to do it?
> -- 
> Pertti
> _______________________________________________
> MeeGo-packaging mailing list
> MeeGo-packaging at meego.com
> http://lists.meego.com/listinfo/meego-packaging