We have been using TRAC 0.11.1 for quite some time now and have a lot of projects running with it. Now we are facing a migration to a new server and would like to start using TRAC 0.12.2.
Of course migrating all 0.11.1 projects to 0.12.2 would be possible, but would also be a lot of work while a lot of them only remain for reference. For new projects, we would like to benefit from the new functionality in 0.12.2.
So, we would like to combine a 0.11 installation to maintain the existing projects and start using 0.12 for the new projects. We run Python 2.6.6 on Windows with mod_wsgi in Apache. We have studied a solution on the TRAC website, but it is for Linux. Also information on the mod_wsgi wiki (http://code.google.com/p/modwsgi/wiki/IntegrationWithTrac) seems to work only on Linux, as it uses a daemon mode which is not available on Windows.
Anybody has suggestions how to use both TRAC 0.11 and 0.12 on the same Python installation on Windows?
install both versions of Trac outside of the Python environment (like c:\trac\11 and c:\trac\12)
define separate virtual hosts for each group of projects
in each virtual host at the beginning of each .wsgi alter the path like:
.
import os
import sys
sys.path.insert(0, 'c:/trac/11')
# sys.path.insert(0, 'c:/trac/12')
I'm currently using this method for Django (on Apache + mod_wsgi)
Related
I installed IntelliJ and WebStorm on my Linux Mint distro. The problem I have is that I cannot use the integrated terminal on both of the software. In both of them there is a problem with my bash binary location. I researched and saw that the software manager in Linux Mint installs flatpak software by default, and that it works as a sort of a container. I tried to change the location of my bash binary to var/run/host.. but it didn't seem to work.
I read that people solve this by installing the tar version of the software or using snapd. Since snapd is not supported by Linux Mint, what are my alternatives? Can I somehow give access to my software to use my bash, npm, etc... and if not, why is it that flatpak makes these things so difficult?..
Flatpak works as a sandbox environment - each pack has its own runtime environment and because of security reasons, flatpak apps do not have direct access to host files. There could be a lot of problems due to this.
Please try reinstalling the IDE using one of the officially recommended options (https://www.jetbrains.com/help/webstorm/installation-guide.html) - download the tar.gz from https://www.jetbrains.com/webstorm/download/#section=linux, or use the toolbox app to manage installations
I want to install the Orange3-spark addon,
I checked the requirements and it was (Apache Spark, Pandas, and orange3),
Problem Description
I installed it according to the order below, added the spark addon (GUI approach), no error messages, but there were no widgets shown in the Spark ML section.. The Spark ML section is empty,
Installation Steps
Installed Apache Spark 2.1.1 with Hadoop 2.7 on a Windows 10 machine.
Scala 2.11.8 (comes with Spark)
Checked Spark using (spark-shell) in command prompt
Installed Anaconda 4.4.0 Python 3.6 version
Verified that Pandas is installed within Anaconda
Installed Orange version 3.4.4
Installed Spark Addon (GUI way from orange)
Can you please instruct me on what to do ?
I have never used Python before, I know the job of most of the above-mentioned components, however, this is the first time that I install any of the above. So please bear with me and be clear with your comments ;))
I had a similar problem with the network add on in Orange3 and overcame it by doing a terminal install with root access via sudo instead of the canvas gui install. Try a command line install running as administrator via runas.
I am having the Neo4j community version 2.3.0 installed on my windows machine.I am trying to install neo4j-shell tools in my windows machine.I tried copying the jar files and its not helping. Is there a limitation of this feature in community version?
There is no limit, you just have to put them in the right directory.
It works best with the zip distribution on windows. Then you can just follow the readme.
I have the python package in Cygwin on Windows 7. However, typing
python -V
returns
Python 2.6.8
This is a pretty low version of Python... I could use Python 3.x (whatever version is newest, preferably). I've seen some people say you have to download a .zip or .tar manually to get it (similar to this question). My questions are as follows (please note this is NOT a duplicate of the linked question):
Can I get Python 3.x somehow using the Cygwin package manager?
Can/should I get rid of Python 2.6 if I manage to get Python 3.x running? None of my code runs on anything specific to Python 2.6.
Thanks
As others have noted, the version of Python 2.6 that's installed with Cygwin is recent; Python release numbers are not linear with respect to time. The Python releases page details which versions were released on which date.
You can install Python3 if you want, using Cygwin Ports. This is a collection of Cygwin packages that are not ready for general release on the main Cygwin mirrors, but have been compiled ready to be used on Cygwin. I've written some instructions over on SuperUser which describe in more detail how to do this.
(I'd avoid installing from source, as Lennart suggests, as I'd expect this will require non-trivial fixes to make it work on Cygwin.)
As noted in the above-linked SuperUser question, there's no need to uninstall Python 2.6 to install Python 3; the two run happily side-by-side.
That said, beware your claim that "None of my code runs on anything specific to Python 2.6": Python 3.x is not back compatible with Python 2.x, and code written for Python 2.x will generally not work on Python 3.x without work to adapt it. The Python 3.0.1 What's New Guide has a good overview of the changes in Python 3.x.
Update: As of Wed 25 July 2012, Python 3.2.3 is included in the standard Cygwin installer. Just run Cygwin's setup.exe again (download it from cygwin.com again if you need to), and you should be able to select and install it like any other package.
To create executable files (windows) I assume that we should use one of them:
Py2exe or PyInstaller.
What are the difference between them?
Py2exe and PyInstaller both are wrappers but here are few differences that I noticed,
Py2exe is compatible with python2.4+ including python3.0 & 3.1 whereas PyInstaller is currently, compatible with python 2.7 and 3.3–3.5
As far I know, Py2exe didn't support signing whereas Pyinstaller has support for signing from version 1.4
In PyInstaller it is easy to create one exe, By default both create a bunch of exes & dlls.
In py2exe its easier to embed manifest file in exe, useful for run as administrator mode in windows vista and beyond.
Pyinstaller is modular and has a feature of hooks to include files in the build that you like. I don't know about this feature in py2exe.
Hope this helps you in your decision making.
[Update] - It looks like PyInstaller is actively developed (https://github.com/pyinstaller/pyinstaller/) and released. py2exe is still using sourceforge and its release cycle is very random on pypi there is no build after 2014 and their code show development in 2017 as well (https://sourceforge.net/p/py2exe/svn/HEAD/tree/trunk/py2exe-3/py2exe/). So, I recommend using pyinstaller till the time py2exe stabilizes its release cycle in favor of developers.
There is a fork of py2exe that is being actively developed to support ongoing versions of Python, https://github.com/albertosottile/py2exe, currently at v0.9.3.2 which works with Python 3.7.
I've used it on a small project and it works as expected, producing a working executable. Download the correct version from the releases page and install with pip.
Update 2020-11-06:
As per LolPython's comment, this fork now redirects to the official repo so use that instead:
https://github.com/py2exe/py2exe
From the message of the wikipedia,py2exe is not active for long time :
Stable release: 0.9.2.2 for Python 3 /; 21 October 2014; 0.6.9 for Python 2 /; 15 November 2008
So I advise to use the pyinstaller.....
But now the pyinstaller also meet the problemThe offical website of pyinstaller:
Help keeping PyInstaller alive: Maintaining PyInstaller is a huge amount of work. PyInstaller development can only continue if users and companies provide sustainable funding. See Funding PyInstaller for how to support PyInstaller.