Thank you very much, "tg-admin info" is now working.
But unfortunately the next question is now that "quickstart" gives an
error related to the template engine "Cheetah" :
Error in the Python code which Cheetah generated for this template:
=======================================
EOL while scanning single-quote string
(cheetah_DynamicallyCompiledCheetahTemplate_2007082918071928753.py,
line 319)
..................................................
It seems that there are probably many more dammage resulting from the
default TurboGears installation from KUBUNTU ?
I have now 2 machines on my desk:
- Machine A : my main desktop with the standard KUBUNTU 7.04.
TurboGears was initially installed using Adept.
RuleDispatch-0.5a0.dev_r2306-py2.5-linux
- Machine B : a notebook also with the standard KUBUNTU 7.04.
TurboGears was directly "easy_installed" and works well.
The most obvious difference between these 2 machines are in the
directories. I see multiple instance of the same files in the same
machine, in different directories.
What is the intended strategy of TurboGears ?
/usr/local/lib/python2.5/site-package/.......
/usr/lib/python2.5/site-package/.......
It looks that the second one could be the right one for TurboGears ?
It seems that KUBUNTU did install the incompatible files in /usr/local/
lib/... rather than /usr/lib/...
I see "TurboCheetah-0.9.5-py2.5.egg" and related files several
times
/usr/share/python-support/python-cheetah/Cheetah/CheetahWrapper.py
/usr/lib/python2.5/site-packages/Cheetah-2.0rc8-py2.5linux-
i686.egg/Cheetah/CheetahWrapper.py
/usr/local/lib/python2.5/site-packages/TurboCheetah-0.9.5-
py2.5.egg/turbocheetah/cheetahsupport.py
/usr/lib/python2.5/site-packages/TurboCheetah-0.9.5-py2.5.egg/
turbocheetah/cheetahsupport.py
How could I clean machine A.
I am hesitating to dare to use Adept to remove TurboGears, because a
fear that I would remove too many essential core Python modules.
As far as I known TurboGears depends on many standard Python features,
normally maintained by adept.
I could try to remove manually from /usr/local/lib/... everything
looking related to TurboGears and to run "easy_install" again.
But the next question is that a few files could be necessary, in other
directories than the "site-package" and somewhere in a PATH ?
Later on, may I continue to use the standard maintenance from KUBUNTU
based on adept ? What would happen if some generic Python libraries
would be updated ????
Nevertheless I did try to remove the installation according to UBUNTU
and to reinstall everything
sudo apt-get remove python-turbogears
as required I did also try " sudo apt-get autoremove " but a few lock
file problems did arise., /va/lib/dpkg/lock ..... ?
New installation attempt:
sudo easy_install --prefix /usr/local -f
http://www.tubogears.org/download/index.html
TurboGears[standard]
But now an other kind of Error:
[EMAIL PROTECTED]:~/TBG$ sudo easy_install --prefix /usr/local -f
http://www.tubogears.org/download/index.html TurboGears[standard]
Searching for TurboGears[standard]
Best match: TurboGears 1.0.3.2
Processing TurboGears-1.0.3.2-py2.5.egg
TurboGears 1.0.3.2 is already the active version in easy-install.pth
Installing tg-admin script to /usr/local/bin
Using /usr/local/lib/python2.5/site-packages/TurboGears-1.0.3.2-
py2.5.egg
Processing dependencies for TurboGears[standard]
Searching for Cheetah>=2.0rc7
Reading http://www.tubogears.org/download/index.html
error: Download error: (-2, 'Name or service not known')
Again a problem related to Cheetah ??????????
Comments :
The following documentation is coming from KUBUNTU. As a beginner I
do not well understand the meaning of "dh_pysupport", maybe on itself
a clever idea, but but obviously not coordinated with the recent
ongoing development of TurboGears:
********************************************************************************************************
Python-support is a tool to handle byte-compilation of python modules
when there are several python versions installed on the system.
How does it work?
=================
Python-support looks for modules in /usr/share/python-support.
* Private modules (.py files that shouldn't be installed in the
default
sys.path) are handled through a foo.dirs file, which contains a
list
of directories in which to find modules. If the directory contains
a
.pyversion file, they will be bytecompiled with the python version
described inside, otherwise the current python version will be
used.
* Public modules (.py files that should be installed in the default
sys.path) are handled through a foo/ subdirectory, containing a
hierarchy as normally found in /usr/lib/pythonX.Y/site-packages/.
They will be installed and bytecompiled in each python specific
directory: /var/lib/python-support/pythonX.Y/. If a .version file
is
found in /usr/share/python-support/foo/, it will be parsed for the
list of python versions the module supports. It should look like
e.g.:
2.2,2.4-
for a package supporting python2.2, and all versions starting from
python2.4.
* Public extensions (.so files) are handled just like public
modules,
but extensions for each pythonX.Y version will be searched in
/usr/lib/python-support/foo/pythonX.Y/ and installed in
/var/lib/python-support/pythonX.Y/ together with the corresponding
modules. No .version file is needed in this case, and the modules
will be installed only for the python versions supported by the
extensions.
How to make a package using it?
===============================
All the work is done using dh_pysupport. Most packages built for the
"old" policy can just be changed to use dh_pysupport instead of
dh_python, and this should work. Packages building binary extensions
should also be changed to build the extensions for all python
versions
in a single package.
*** You don't need X[BS]-Python-Version fields. You don't need ***
*** debian/pycompat. Just remove all of these. ***
(You can also use dh_python to generate the dependencies instead, but
this is not recommended as it is less clever in their generation. In
this case, you'll need the debian/pycompat file.)
Of course, don't forget the dependency fields:
Build-Depends: python-support (>= 0.4), debhelper(>= 5)
Depends: ${python:Depends}
If you're including public modules or extensions, you can also add
the
optional field:
Provides: ${python:Provides}
For a package with only private modules
---------------------------------------
In this case, the rules file will probably look like this:
build:
make ...
install:
make install DESTDIR=debian/foo/
binary-indep:
...
dh_pysupport
dh_installdeb
...
If the private modules are not in a default directory (like
/usr/share/$package or /usr/lib/$package) you should pass the
directory
to dh_pysupport and dh_python:
dh_pysupport /usr/share/someframework/foo
If the modules need a specific python version, you can pass the -V
argument to dh_pysupport; it works exactly like for the old dh_python.
dh_pysupport -V2.4
For a package with public modules
---------------------------------
If the module doesn't work with all python versions, you should setup
a
debian/pyversions file. If the package needs python >= 2.3, it will
look
like :
2.3-
This file will be installed in /usr/share/python-support/foo/.version.
The rules file will look like this:
build:
...
python setup.py build
install:
...
python setup.py install --root=$(CURDIR)/debian/python-foo
binary-indep:
...
dh_pysupport
dh_installdeb
...
For a package with public C extensions:
---------------------------------------
First of all, you should build-depend on python-all-dev.
If you want to build the extension only for some python versions, you
should create a debian/pyversions file as described earlier, and set
in
the rules file:
PYVERS=$(shell pyversions -vr)
You need to build-depend on python (>= 2.3.5-11) for this to work.
Otherwise, you can just build the extensions for all supported python
versions:
PYVERS=$(shell pyversions -vs)
The rest of the rules file will look like:
build: $(PYVERS:%=build-python%)
touch $@
build-python%:
python$* setup.py build
touch $@
install: build $(PYVERS:%=install-python%)
install-python%:
python$* setup.py install --root $(CURDIR)/debian/python-foo
binary-arch:
...
dh_pysupport
dh_installdeb
...
********************************************************************************************************
Etienne
On Aug 9, 2:58 pm, Mikkel Høgh <[EMAIL PROTECTED]> wrote:
> On Aug 9, 11:58 am,saliez<[EMAIL PROTECTED]> wrote:
>
>
>
> > Thank you very much for your message.
>
> > Sorry, I would best believe it should work, but actually it does not
> > yet.
>
> > - Perhaps somewhere a stupid problem in the version of some component
> > or in a PATH ?
>
> > - I was initially trying to make the installation using the automatic
> > installation provided by Kubuntu using the " adept " system.
> > In general I must say that it works very well and upgrades are managed
> > automatically.
> > However I understand that Turbogears is in very active developments
> > and that Canonical cannot support this rapid evolution before a long
> > delay of perhaps a year.
> > The trouble could come from the fact I am not sure to have removed all
> > components of that initial installation which did fail.
>
> > - A new " easy_install " in " /usr/local/lib/python2.5/site-packages/
> > ".
> > Using " easy-install " seems OK, but " tg-admin info " gives an "
> > OverFlowError ".
> > I have no idea how to investigate that further.
>
> > - If not otherwise possible and in order not to delay other projects,
> > it would perhaps become more efficient to buy a new machine and to try
> > easy_install on a clean installation of Kubuntu 7.04 ?
>
> > - If that does not even works, I could start again with the
> > installation of an other distribution of Linux.
>
> > I am going now on some vacations, but after that i need a solution to
> > install Turbogears and to hmake time free to work on the content of
> > the project.
>
> > I send you an Email with my notes in annex.
>
> > Many thanks in advance
>
> > EtienneSaliez
>
> > On Aug 8, 9:07 pm, Paul Howell <[EMAIL PROTECTED]> wrote:
>
> > >saliezwrote:
>
> > > > How is it possible to install TurboGears in Kubuntu 7.04 ???
>
> > > > ( 1 ) Installation based on Kubuntu adept does not work and is based
> > > > on incompatible obsolete versions.
> > > > Forget it. At the side of Canonical they propose Turbogears in their
> > > > installation list, but they cannot provide any support.
>
> > > > ( 2 ) easy_install :
> > > > Installation based on the documentation provided by TurboGears at "
> > > >http://docs.turbogears.org/1.0/InstallUbuntu"; did not work too.
> > > > " tg-admin info " gives always an " OverFlowError ".
>
> > > > I do absolutely no know how but it did at once work on my laptop.
>
> > > > Turbogears looks in principle very good, but I cannot start to work on
> > > > a project if there is no reliable installation procedure ????
>
> > > > Later on I would also need to install on a server based on gentoo;
> > > > Is it possible ????
>
> > > <error msg snipt>
>
> > > This should work (as per many previous questions on this
> > > list):http://docs.turbogears.org/1.0/InstallUbuntu
> > > find by searching install Ubuntu in docs.turbogears.org
>
> > > re: gentoo, see this:http://docs.turbogears.org/1.0/InstallNix
>
> > > Paul
>
> Hi Etienne,
>
> The problem seems to come from the fact that you are still using som
> of Ubuntu's packages for some of TurboGears' components.
> As you can see in the traceback it complains about files from /var/lib/
> python-support/python2.5/dispatch/
> This indicates that you have the Ubuntu package 'python-dispatch'
> installed. You can remote it with Adept.
> When you have removed it, try running this:
> sudo easy_install -U RuleDispatch
> That should install a version of RuleDispatch that works with
> TurboGears. When that is done, your problem should be solved.
>
> Kind regards,
> Mikkel Høgh
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TurboGears" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/turbogears?hl=en
-~----------~----~----~----~------~----~------~--~---
