SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Is python 2.7 going to appear in Slackware anytime soon? I see that -current only has 2.6.6. I really like Calibre (an ebook management and conversion program) and the latest versions need python 2.7 (the SBo slackbuild has stopped at the last version that could be done with python 2.6). I can install 2.7 side by side with an older version, but I was hoping not to have to do that ...
By the way, Calibre would be a really good addition to Slackware too.
As far as the python 2.7 dependency in calibre is concerned, it should work just fine with python 2.6. I believe the developer just wants to support 1 version of python.
I just happen to try and build calibre 0.7.46 in an updated Slackware -current VM yesterday (2/19/11). It fails to build even on current despite not having python 2.7. As far as I can see it, sip, PyQt, and kdebindings need to be upgraded in that order for calibre to build (actually kdebindings just need to rebuilt).
This is just a wild guess, but I wouldn't bet for Python 2.7 to be in the next stable release. I'm pretty sure we're somewhat close to a new release, and upgrading Python would require a lot of packages to be rebuilt for it. My bet would be in the next release cycle.
As far as the python 2.7 dependency in calibre is concerned, it should work just fine with python 2.6. I believe the developer just wants to support 1 version of python.
That's what I thought and was building it using the SBo package that exists for 0.7.37 for up to 0.7.44. However I then noticed that some functions were failing silently. Thus I moved back to 0.7.37 which builds cleanly in Slackware 13.1
Quote:
Originally Posted by larryhaja
I just happen to try and build calibre 0.7.46 in an updated Slackware -current VM yesterday (2/19/11). It fails to build even on current despite not having python 2.7. As far as I can see it, sip, PyQt, and kdebindings need to be upgraded in that order for calibre to build (actually kdebindings just need to rebuilt).
Also, I think QScintilla needs to be upgraded.
At least up to Calibre 0.7.44 there is no need for any upgrades, the package in SBo works fine.
I will try to install python 2.7 side by side with the current version in Slackware to build the latest Calibre (it really is that good)
This is just a wild guess, but I wouldn't bet for Python 2.7 to be in the next stable release. I'm pretty sure we're somewhat close to a new release, and upgrading Python would require a lot of packages to be rebuilt for it. My bet would be in the next release cycle.
Yes, I thought so too... I like the stability of Slackware, but in this case it is a bit behind; they just released python 3.2 ...
Python 3.x is a different branch and language, and there are many more aspects to take into account, like compatibility with 3rd party packages. The most recent Python 2 version, on the other hand, is 2.7. Debian is shipping Python 2.6, so are doing Novell, Red Hat or Ubuntu. Slackware is no different or behind from that point of view.
That's what I thought and was building it using the SBo package that exists for 0.7.37 for up to 0.7.44. However I then noticed that some functions were failing silently.
Intersting...can you give me an example of a function that is failing? I'm not aware of this. I submitted a build script to SBo on version 0.7.45, which is the last version that builds on 13.1 and current. If there is an issue then I'd like to retract that build.
Intersting...can you give me an example of a function that is failing? I'm not aware of this. I submitted a build script to SBo on version 0.7.45, which is the last version that builds on 13.1 and current. If there is an issue then I'd like to retract that build.
Oops, this was a while ago, I'll have to go back to 0.7.44 to see what was not working.
BTW, why did versions above 0.7.45 fail to build in slackware? What is missing? This is really a good program and it would be great to get updated versions in slackware. (this thread is changing to calibre, we should probably continue in a new thread)
BTW, why did versions above 0.7.45 fail to build in slackware? What is missing?
sip >= 4.12, PyQt >= 4.8.2, and Qt >= 4.7.0. Although python 2.7 is now a requirement it still will compile with 2.6. Not sure of any problems using 2.6.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.