Sigil 0.8.0 Released

[varlog]

I've just checked: lots of python but development tools seem not to be there (Ubuntu 14.04 64bit). I can use plugins.

[BetterRed]

Originally Posted by JSWolf

The two plugins I've installed for Sigil are for Python 2. I do not have any developer tools installed and the one plugin I did try worked as advertised.

Then why this

Originally Posted by Doitsu to crutledge

Did you install Python from the official website? If so you might be missing some required libraries. You may want to uninstall your version and install ActivePython, which will install everything that you need.

I note that Sigil 0.8.0 auto installs the 2013 C++ Re-distributable package (I think), personally I would rather it didn't do that automatically, and give me the option of doing it manually, perhaps with a link to where to get it.


Maybe the Sigil Forum needs to have a Developers Sub-forum and a Users Sub-forum - the plug-in threads could be sticky's in the latter.

BR

[blackest]

Originally Posted by varlog

blackest hmmm?

https://drive.google.com/file/d/0BwT...it?usp=sharing

hopefully that link should work

[JSWolf]

The version of Python I have installed is from the OFFICIAL website at python.org. I have pycrypto installed, but that's about it. The version I have a 2.7.6 32-bit.

[BetterRed]

@JSWolf - what happens if you uninstall that version of Python, do the plugins still work?

BR

[JSWolf]

Originally Posted by BetterRed

@JSWolf - what happens if you uninstall that version of Python, do the plugins still work?

BR

I would say the plugins would not work as you do have to specify where your installation(s) of Python is/are in the plugin setup.

[poxalew]

Originally Posted by BetterRed

@JSWolf - what happens if you uninstall that version of Python, do the plugins still work?

BR

That will depend on the plugin. If you uninstall the last version of a 2.x Python runtime you had on a system, then plugins requiring a 2.x Python runtime will stop working.

Python runtimes generally ensure good forward compatibility as long as you stay on a major version; i.e., code written for 2.4.x will typically work on 2.5.x, 2.6.x, and 2.7.x, and code written for 3.0.x will tend to work on 3.2.x, 3.3.x, 3.4.x.

Compatibility between minor releases (i.e., 2.7.6 versus 2.7.7 versus 2.7.8 etc) is almost a given since they're bugfix-only releases; problems there happen very, very rarely, and you can generally run code written for 2.7.something on earlier 2.7 versions. This is especially true for Python 2.x, since it's in conservation mode (no newer 2.x versions will be released, just bugfixes.)

[BetterRed]

Originally Posted by DiapDealer

that's why it would be better for you to spend some time trying to understand how the Python plugin framework is currently set up...

Originally Posted by JSWolf

I would say the plugins would not work as you do have to specify where your installation(s) of Python is/are in the plugin setup.

Originally Posted by poxalew

That will depend on the plugin. If you uninstall the last version of a 2.x Python runtime you had on a system, then plugins requiring a 2.x Python runtime will stop working.

Python runtimes generally ensure good forward compatibility as long as you stay on a major version; i.e., code written for 2.4.x will typically work on 2.5.x, 2.6.x, and 2.7.x, and code written for 3.0.x will tend to work on 3.2.x, 3.3.x, 3.4.x.

Originally Posted by BetterRed

I have a swag of applications that have plug-ins - calibre, notepad++, irfanview, The Gimp, Fast Picture Viewer etc. AFAIK none of them require me to download developer tools to use any of the plug-ins.

For me the main issue is not this or that version, or this or that implementation of Python - its the fact that I have to install Python at all, at all.

BR

[blackest]

Originally Posted by BetterRed

For me the main issue is not this or that version, or this or that implementation of Python - its the fact that I have to install Python at all, at all.

BR

On Osx or Linux, you will almost certainly have python built in to the os install
If you have calibre there is a fair chance you will have python extensions anyway.

[KevinH]

Hi,
I am not sure what you mean by "developer tools" exactly. The plugins require you to have a python interpeter installed if you want to run plugins since they are written in python. Python is quite a popular scripting language. Calibre is in fact a rather large python program. Calibre comes with its own specially modified and expanded version of python.

Instead of packaging up python into Sigil and greatly growing the size of the Sigil download and possibly duplicating already existing python installations, we simply allow users to use any python interpreter that they already have installed on their system. Most Mac OS X and Linux users already have python2.7 installed on them as it is a standard part of their OS. Windows users can download and install a free community edition of ActiveState's ActivePython2.7.X to install. Just like you download and install any other software package. Once installed, Sigil can be set to use your installed python2.7 package to run the plugins.

As I don't see plugin support going away, it is not a "for-now only" thing. That said, if you don't want to use any of the plugins, you don't need python, and Sigil will continue to run just fine.

Hope this helps.

KevinH

Originally Posted by BetterRed

Dumb question - am I right in thinking that Sigil require the user to install the Python developer tools (and perhaps multiple versions thereof) to use its plug-ins. And is this a 'for now' or a 'for ever' situation.

I have a swag of applications that have plug-ins - calibre, notepad++, irfanview, The Gimp, Fast Picture Viewer etc. AFAIK none of them require me to download developer tools to use any of the plug-ins.

BR

[KevinH]

Originally Posted by BetterRed

I note that Sigil 0.8.0 auto installs the 2013 C++ Re-distributable package (I think), personally I would rather it didn't do that automatically, and give me the option of doing it manually, perhaps with a link to where to get it.

BR

Sigil itself is written in C++ and the builds made by user-none use the latest Microsoft VisualStudio 2013 compiler. This compiler requires the user to have the proper runtime library to make any compiled application work.

KevinH

[KevinH]

Originally Posted by Jellby

Any update to FlightCrew?

Not specifically that I know of, but user-none would be the authority on that. Is there a bug or change you had in mind?

Thanks,

Kevin

[BetterRed]

Originally Posted by KevinH

Sigil itself is written in C++ and the builds made by user-none use the latest Microsoft VisualStudio 2013 compiler. This compiler requires the user to have the proper runtime library to make any compiled application work.

KevinH

I know what it is, its just that I prefer to do my own configuration management rather than having code editing applications do it for me - without asking.

FWIW I have 40+ years in IT. ~30 in s/w development writing in Assembler, C, C++ and Ada. The last few years were in system & operations management.

BR

[DiapDealer]

Originally Posted by BetterRed

FWIW I have 40+ years in IT. ~30 in s/w development writing in Assembler, C, C++ and Ada. The last few years were in system & operations management.

You should have no trouble building Sigil from source, then. You can make it sing and dance to any tune you like that way.

[KevinH]

Originally Posted by BetterRed

I know what it is, its just that I prefer to do my own configuration management rather than having code editing applications do it for me - without asking.

FWIW I have 40+ years in IT. ~30 in s/w development writing in Assembler, C, C++ and Ada. The last few years were in system & operations management.

BR

I am now confused. If you have 40+ years of Software development / IT experience, then why did you even ask about python since you had to know it was an interpreted scripting language? And why on earth would you care about an official Microsoft C++ runtime dll being included? The days of DLL hell are long gone and uniquely named shared libraries won't hurt your system. If fact Microsoft gives explicit permission to package the dll with your installer/package otherwise the executable simply won't work.

KevinH