MobileRead Forums - View Single Post

Agama · 06-24-2012, 11:10 AM

The source update only took about 30 mins and Tweak ePub had indeed changed. I finally got version 1 of my plugin working and it was a satisfying moment

, so thanks for all the help.

I then decided to play with the interface_demo plugin to increase my understanding of plugins and python. I broke it a few times and learned from the experience, then I removed some code which I expected would break it – but didn't! At the top of each .py file there is:

Code:

from __future__ import (unicode_literals, division, absolute_import,
 print_function)

I expected to get an error which would give me a module and line number to look at, but the plugin still worked. So what does this code do?

Also there are couple of comment lines at the top:

Code:

#!/usr/bin/env python
# vim:fileencoding=UTF-8:ts=4:sw=4:sta:et:sts=4:ai

Are these used by any process or just for information?

06-24-2012, 11:10 AM	#20
Agama Guru Posts: 776 Karma: 2751519 Join Date: Jul 2010 Location: UK Device: PW2, Nexus7	The source update only took about 30 mins and Tweak ePub had indeed changed. I finally got version 1 of my plugin working and it was a satisfying moment , so thanks for all the help. I then decided to play with the interface_demo plugin to increase my understanding of plugins and python. I broke it a few times and learned from the experience, then I removed some code which I expected would break it – but didn't! At the top of each .py file there is: Code: from __future__ import (unicode_literals, division, absolute_import, print_function) I expected to get an error which would give me a module and line number to look at, but the plugin still worked. So what does this code do? Also there are couple of comment lines at the top: Code: #!/usr/bin/env python # vim:fileencoding=UTF-8:ts=4:sw=4:sta:et:sts=4:ai Are these used by any process or just for information?