Re: Bad sorting on source

On Tue, Feb 18, 2014 at 7:41 AM, Stefan Kaltenbrunner <
stefan(at)kaltenbrunner(dot)cc> wrote:

> On 02/18/2014 06:35 AM, Ian Lawrence Barwick wrote:
> > 2014-02-18 14:14 GMT+09:00 Ian Lawrence Barwick <barwick(at)gmail(dot)com>:
> >> 2014-02-04 20:19 GMT+09:00 Magnus Hagander <magnus(at)hagander(dot)net>:
> >>> On Mon, Feb 3, 2014 at 11:34 PM, Ian Lawrence Barwick <
> barwick(at)gmail(dot)com>
> >>> wrote:
> >>>>
> >>>> 2014-02-04 Joshua D. Drake <jd(at)commandprompt(dot)com>:
> >>>>>
> >>>>> Hey,
> >>>>>
> >>>>> When we go to download PostgreSQL from the website we show ancient
> >>>>> versions
> >>>>> first:
> >>>>>
> >>>>> http://www.postgresql.org/ftp/source/
> >>>>>
> >>>>> We should show the current versions first.
> >>>>
> >>>> I get my source mainly from GIT these days, but now you mention it
> I've
> >>>> been
> >>>> annoyed by having to scroll down the growing list to find the latest
> >>>> versions,
> >>>> so +1 from me. I can put my keyboard where my mouth is if there's some
> >>>> coding needed to fix this.
> >>>
> >>>
> >>> I know somebody was working on this before, but I can't actually
> remember
> >>> who it was :O
> >>>
> >>> I don't think I've seen a patch.
> >>>
> >>> Thus you are more than welcome to contribute :) git.postgresql.org,
> project
> >>> is "pgweb" :)
> >>
> >> (...time passes...)
> >>
> >> Stupid question from someone not terribly familiar with Python
> frameworks -
> >> the installation instructions say "django *version 1.4*", is 1.4 a
> >> specific requirement
> >> or would later versions work? (I have 1.5.1 available right now).
> >
> > OK, it looks like 1.4 is needed, I get a "No module named simple" error
> > with 1.5.1.
>
> yeah - there is usually not a lot of testing done on newer/older
> versions of python/django than what is in Debian Wheezy (or rather
> Debian stable at a given time) because that is our deployment target for
> production.
> Needless to say that we will also take patches for making it work with
> newer versions as well to save us some time on the next upgrade ;)
>

Absolutely. It's probably not a huge set of updates to work, but they do
need to be done :) Of course, the next debian stable will have Django 1.6,
so we're likely just going to bypass 1.5.

And of course, any such patches need to be backwards compatible.

Personally I just set up a virtualenv with exactly the same version, to
make sure I test on the same thing that goes in prod.

--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/