Building from subversion

0 views
Skip to first unread message

Bill Woodward

unread,
Oct 7, 2005, 11:13:31 AM10/7/05
to turbo...@googlegroups.com, wpw...@gmail.com
Good morning,

I've downloaded the latest (I think) version of TurboGears via
subversion ("svn co http://www.turbogears.org/svn/turbogears/trunk
turbogears"), and I go to build the development version, as detailed
on http://www.turbogears.org/community/contributing.html, by running:

python setup.py develop

but when I do this, I start to do a build, and get the following error:

--- snip ---
Installed c:\documents and settings\william_woodward\turbogears
Processing dependencies for TurboGears==0.8a1dev-r43
Searching for CherryPy>=2.1.0-betadev
Reading http://www.python.org/pypi/CherryPy/
Reading http://www.cherrypy.org
No local packages or download links found for CherryPy>=2.1.0-betadev
error: Could not find distribution for
Requirement.parse('CherryPy>=2.1.0-betadev')
--- end snip ----

I also saw this error with the Kid egg, but solved it by downloading
the latest (0.7a) Kid egg file. I can also see all of the source in
turbogears/thirdparty, it just looks like it's not getting built and
used.

So, what step am I missiing? I assume I need to do something to
create eggs from the third-party components, but I can't figure out
how to do it.

TIA,
- Bill

--
Bill Woodward wpw...@saifa.net http://www.saifa.net

"I have more trouble with D. L. Moody than with any other man I ever
met." -- D. L. Moody
s/D. L. Moody/Bill Woodward/g

bon...@gmail.com

unread,
Oct 7, 2005, 11:23:42 AM10/7/05
to TurboGears
first, you need to follow exactly the installation instruction on
TurboGears(to kick start a base, could be outdated but doesn't matter).
Then you can do your svn upgrade as described above, including any new
Kid, Cherrypy, SQLObject etc.

TurboGears has a pretty long list of dependencies and they are only
available on TurboGears(thus the kick start), not through the generic
setuptools mechanism(search through PyPI).

Bill Woodward

unread,
Oct 7, 2005, 11:36:09 AM10/7/05
to turbo...@googlegroups.com
Ah, I had blown away my turbogears 0.5.1 version because I had
received an error about Kid being an older version. So, should I have
done an upgrade instead? If so, how?

Thanks again,

David Stanek

unread,
Oct 7, 2005, 11:47:22 AM10/7/05
to turbo...@googlegroups.com
So you are saying to first install TurboGears normally as most users would and then do the svn checkout?

David

On 10/7/05, bon...@gmail.com <bon...@gmail.com> wrote:



--
David Stanek
www.roninds.net

bon...@gmail.com

unread,
Oct 7, 2005, 11:50:08 AM10/7/05
to TurboGears
just install 0.51. Then checkout the SVN trunk of Kid or whatever and
upgrade them one by one. Until there is a very mature archive network
like CPAN, this should be a FAQ.

bon...@gmail.com

unread,
Oct 7, 2005, 11:52:23 AM10/7/05
to TurboGears
YES. I have gone through all these before. setuptools sounds great
except that the infrastructure is not there yet.

David Stanek

unread,
Oct 7, 2005, 11:56:32 AM10/7/05
to turbo...@googlegroups.com
That is probably better than what I had done. I just grabbed the eggs from the TurboGears download page and since I am on Linux I built a cElementTree egg. Then I wrote a little shell script to set my PATH and PYTHONPATH.

David

On 10/7/05, bon...@gmail.com <bon...@gmail.com> wrote:

YES. I have gone through all these before. setuptools sounds great
except that the infrastructure is not there yet.




--
David Stanek
www.roninds.net

Bill Woodward

unread,
Oct 7, 2005, 7:04:17 PM10/7/05
to turbo...@googlegroups.com
On 10/7/05, David Stanek <ron...@gmail.com> wrote:
> That is probably better than what I had done. I just grabbed the eggs from
> the TurboGears download page and since I am on Linux I built a cElementTree
> egg. Then I wrote a little shell script to set my PATH and PYTHONPATH.
>

Well, I'm still working on trying to get my TurboGears upgraded. I
have re-installed the 0.5.1 version, then checked out the latest
subversion source, gone into the thirdparty directories and run
'python setup.py install' in each of them (excepy for mochikit). Then
I pop back to the 'turbogears' directory, where I checked out the
subversion trunk, and run 'python setup.py install'. I get a
ValueError exeception containing the text:

"ValueError: ("Missing 'Version:' header and/or PKG-INFO file",
TurboGears [unknown version] (c:\documents and
settings\william_woodward\turbogears))"

Now, I could swear that I did not get this error this morning.
Perhaps something was removed in the latest checkin? Where should I
be looking for a 'Version:' header or a 'PKG-INFO' file?

Thanks again,

Bill Woodward

unread,
Oct 7, 2005, 7:19:49 PM10/7/05
to turbo...@googlegroups.com
On 10/7/05, Bill Woodward <wpw...@gmail.com> wrote:
>
> "ValueError: ("Missing 'Version:' header and/or PKG-INFO file",
> TurboGears [unknown version] (c:\documents and
> settings\william_woodward\turbogears))"
>
> Now, I could swear that I did not get this error this morning.
> Perhaps something was removed in the latest checkin? Where should I
> be looking for a 'Version:' header or a 'PKG-INFO' file?
>

So, it looks like maybe the PKG-INFO file, plus several other files,
were removed form the TurboGears.egg-info/ directory in revision 44.
The comments in the rev show that it was intentional, but it seems to
be causing me trouble. Am I missing a step to create the egg info?

Any clues?

Kevin Dangoor

unread,
Oct 7, 2005, 8:50:37 PM10/7/05
to turbo...@googlegroups.com
On 10/7/05, Bill Woodward <wpw...@gmail.com> wrote:
>
> On 10/7/05, Bill Woodward <wpw...@gmail.com> wrote:
> >
> > "ValueError: ("Missing 'Version:' header and/or PKG-INFO file",
> > TurboGears [unknown version] (c:\documents and
> > settings\william_woodward\turbogears))"
> >
> > Now, I could swear that I did not get this error this morning.
> > Perhaps something was removed in the latest checkin? Where should I
> > be looking for a 'Version:' header or a 'PKG-INFO' file?
> >
>
> So, it looks like maybe the PKG-INFO file, plus several other files,
> were removed form the TurboGears.egg-info/ directory in revision 44.
> The comments in the rev show that it was intentional, but it seems to
> be causing me trouble. Am I missing a step to create the egg info?

Yeah, that was intentional, because it was causing conflicts having them there.

Luckily, you can just run

python setup.py egg_info

to get them back.

By the way, CherryPy in the thirdparty directory does not use
setuptools. You need to alter the setup.py to replace "from
distutils.core import setup" with "from setuptools import setup"

Kevin

--
Kevin Dangoor
Author of the Zesty News RSS newsreader

email: k...@blazingthings.com
company: http://www.BlazingThings.com
blog: http://www.BlueSkyOnMars.com

Bill Woodward

unread,
Oct 7, 2005, 9:02:32 PM10/7/05
to turbo...@googlegroups.com
On 10/7/05, Kevin Dangoor <dan...@gmail.com> wrote:
>
> On 10/7/05, Bill Woodward <wpw...@gmail.com> wrote:
> >
> > So, it looks like maybe the PKG-INFO file, plus several other files,
> > were removed form the TurboGears.egg-info/ directory in revision 44.
> > The comments in the rev show that it was intentional, but it seems to
> > be causing me trouble. Am I missing a step to create the egg info?
>
> Yeah, that was intentional, because it was causing conflicts having them there.
>
> Luckily, you can just run
>
> python setup.py egg_info
>
> to get them back.
>

OK, I did that, but I had to remove the TurboGear.egg-info/ directory
to get it to work.

> By the way, CherryPy in the thirdparty directory does not use
> setuptools. You need to alter the setup.py to replace "from
> distutils.core import setup" with "from setuptools import setup"
>

Cool. I'll check that. When I was running 'setup.py install' in the
top-level turbogears source directory, I was getting the CherryPy
version as a missing prereq. Maybe that's why.

Thanks again!

Bill Woodward

unread,
Oct 7, 2005, 9:30:47 PM10/7/05
to turbo...@googlegroups.com, wpw...@gmail.com
On 10/7/05, Bill Woodward <wpw...@gmail.com> wrote:
> Good morning,
>
> I've downloaded the latest (I think) version of TurboGears via
> subversion ("svn co http://www.turbogears.org/svn/turbogears/trunk
> turbogears"), and I go to build the development version, as detailed
> on http://www.turbogears.org/community/contributing.html, by running:
>

OK, I'm still working on this, but here are the steps I'm taking:

1) Blow away the <python install dir>/Lib/site-packages/<whatever>
directories for all of the TurboGears components
2) Run 'python ez_setup.py -f
http://www.turbogears.org/download/index.html TurboGears' to install
the 0.5.1 version of turbogears
3) Run ' svn co http://www.turbogears.org/svn/turbogears/trunk
turbogears' to check out the turbogears source
4) cd into the 'turbogears' directory and remove the
'TurboGears.egg-info' directory.
5) Run 'python ez_setup.py' to get the latest setuptools.
6) Run 'python setup.py egg_info' to recreate the
'TurboGears.egg-info' directory.
7) cd to 'turbogears/thirdparty/formencode' and run 'python setup.py install'
8) cd to 'turbogears/thirdparty/sqlobject' and run 'python setup.py install'
9) cd to 'turbogears/thirdparty/kid' and run 'python setup.py install'
10) cd to 'turbogears/thirdparty/cherrypy' and edit 'setup.py' to
replace the line

"from distutils.core import setup"

with

"from setuptools import setup".

Now run 'python setup.py install'
11) cd to 'turbogears' and run 'python setup.py install'
12) In the toplevel 'turbogears' source directory, edit 'setup.cfg'
and comment out the 'copydirs' line.
13) Now, run 'python setup.py docs' to generate the TurboGears
documentation (which was what led me down this path in the first place
:) )

Whew! All done!

Thanks to everyone for all the help.

Kevin Dangoor

unread,
Oct 7, 2005, 10:47:42 PM10/7/05
to turbo...@googlegroups.com, wpw...@gmail.com
On 10/7/05, Bill Woodward <wpw...@gmail.com> wrote:
> Whew! All done!
>
> Thanks to everyone for all the help.

I'm sure some portion of that can be automated :)

Have a good time in Germany!

Krys Wilken

unread,
Oct 8, 2005, 1:18:53 PM10/8/05
to turbo...@googlegroups.com
It might be worth noting that easy_install.py -f . (note the period,
i.e. current directory) works. -f can use local paths as well as urls.

At work we have MS Proxy (NTLM auth) and McAfee WebShield, so
downloading anything is a royal pain. I really like setuptools, but
having a download and local install capability is critical in my work
environment.

That said, I had to write a script to get setuptools installed from a
local egg.

I will be working on using this knowledge with Inno Setup to make a nice
and friendly stand-alone windows installer for my app. It could be used
for TG too.

Ian, if you are reading this, I'd really love to hear your thoughts on
the use of setuptools (and getting setuptools initially installed)
without needing a network connection. (Admittedly I am not well versed
in eggs as TG is my first real exposure to them. :-)

Hope this helps,
Krys
>www.roninds.net <http://www.roninds.net>
>
>
>

Reply all
Reply to author
Forward
0 new messages