Missing TG 1.5 docs?

[John Boynton]

Hi,

I'm still working with TurboGears 1.5, and would like to review the docs, but all of the links I've tried in http://turbogears.org/1.5/docs return 404 Not Found. Am I out of luck to see documentation for this old version?

Thanks,
John

// John Boynton * Senior Engineer

// www.artandlogic.com

// Art & Logic -- Coding the "impossible."™

[Christoph Zwerschke]

The documentation is still here as source, and can built using Sphinx
with "make html":

https://sourceforge.net/p/turbogears1/code/HEAD/tree/docs/1.5/

I had been the last maintainer of TG 1.5, but haven't touched it since
years. Not sure what we shall do with TG 1.5. Everything is now so
horribly outdated and depending on other outdated and unmaintained
projects. You are forced to use very old versions of these projects to
make things work. Also the 1.5 docs were never completed, and referred
to 1.0 docs for missing parts.

Maybe it's better to not even provide live docs any more because they
are so outdated, incomplete and misleading?

Or, if there is larger interest, maybe I could provide one last bugfix
release with frozen upper limits for the dependencies in the setup.py
(currently there are only lower limits and therefore it will probably
only work with the package index for TG 1.5 on the TurboGears server,
which might also go offline some day). Then I could also provide a last
frozen version of the 1.x docs with notes about the discontinued state
of the project and recommendation to upgrade to TG 2.

-- Chris

[Christoph Zwerschke]

Since there was no feedback regarding this question, and I personally
don't have much interest and use for this any more either, I've decided
to end maintenance of the TurboGears 1.x product line. It has been
sitting idle for too long - some of the dependencies have been
discontinued as well and some have run away with new incompatible
versions. There are also too many subvariants (Kid/Genshi,
SQLObject/SQLAlchemy) and add-on projects (TurboJson/TurboCheetah etc.).
I really don't want to open that can of worms any more.

The source code is still available on SourceForge and PyPI for anyone
who needs it.

-- Chris

[John Boynton]

Hi Chris, thanks for your reply, which I just saw. (I thought I would be notified of thread updates, but didn't get any.)

I'm maintaining and continuing to develop a fairly large codebase based on TG 1.5, so am concerned about the TG 1.5 package index going away. It would be very helpful to have one last bugfix with frozen upper version limits, but perhaps I'm the only one interested in this.

We currently install TG 1.5 using easy_install as per the 1.5 docs for installation in both Vagrant development VMs and in Docker containers for deployment. Looks like our options are to either define base images with the current 1.5 code and its dependencies, or clone the required packages from the TurboGears server (is that possible?).

What do you recommend?

Thanks,

John

[John Boynton]

On Tuesday, March 14, 2017 at 5:54:26 PM UTC-4, John Boynton wrote:

We currently install TG 1.5 using easy_install as per the 1.5 docs for installation in both Vagrant development VMs and in Docker containers for deployment. Looks like our options are to either define base images with the current 1.5 code and its dependencies, or clone the required packages from the TurboGears server (is that possible?).

By "define base images" I mean "define and store base images on our servers" where we could reliably access them and build from them when needed.

[Christoph Zwerschke]

Am 14.03.2017 um 22:54 schrieb John Boynton:
> We currently install TG 1.5 using easy_install as per the 1.5 docs for
> installation in both Vagrant development VMs and in Docker containers
> for deployment. Looks like our options are to either define base images
> with the current 1.5 code and its dependencies, or clone the required
> packages from the TurboGears server (is that possible?).

I would simply clone the current package directory. That should be
simple, e.g. with wget:

cd your-local-package-directory
wget -r -np -nH --cut-dirs=3 \
http://www.turbogears.org/1.5/downloads/current/

You can then install from that package directory any time even without
Internet access, by either serving these files with a local webserver or
directly from the file system with:

easy_install -i file://your-local-package-directory TurboGears

-- Chris

[John Boynton]

Thanks Chris

- John

-- Chris

--
You received this message because you are subscribed to a topic in the Google Groups "TurboGears" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/turbogears/2B4rNtR7UtA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to turbogears+unsubscribe@googlegroups.com.
To post to this group, send email to turbo...@googlegroups.com.
Visit this group at https://groups.google.com/group/turbogears.
For more options, visit https://groups.google.com/d/optout.

[Alessandro Molina]

On Tue, Mar 14, 2017 at 10:54 PM, John Boynton <jboy...@artandlogic.com> wrote:

I'm maintaining and continuing to develop a fairly large codebase based on TG 1.5, so am concerned about the TG 1.5 package index going away. It would be very helpful to have one last bugfix with frozen upper version limits, but perhaps I'm the only one interested in this.

Hi John,

Please also consider pointing out if there is anything we can do to help you upgrade your codebase to TG2.3.

If your project is already Genshi and SQLAlchemy based it's usually something that can be done in a reasonable amount of work.

Bests,

Alessandro 

[John Boynton]

Thanks Alessandro,

We are using SQLAlchemy and genshi. We started down the upgrade path a while back, but it was a nontrivial endeavor, and business needs got in the way of completing the upgrade. It looks like we need to revisit that though, because this application is still in active development with no sign of sunset soon.

John