Django 1.1 is not installable

[Michael Elsdörfer]

$ pip install django==1.1

Downloading/unpacking django==1.1

  Could not find a version that satisfies the requirement django==1.1 (from versions: )

No distributions matching the version for django==1.1

This was working perfectly well not so long ago. I notice 1.1 isn't listed on PyPI either:

http://pypi.python.org/pypi/Django

Michael

[Jacob Kaplan-Moss]

I'm not sure why it's hidden on PyPI, but in the meantime you can get it from https://www.djangoproject.com/download/.

I should point out that 1.1 is woefully out of date and no longer receives security updates. There are probably security vulnerabilities and certainly bugs; you should really upgrade as soon as possible.

Jacob

Michael

--
You received this message because you are subscribed to the Google Groups "Django developers" group.
To post to this group, send email to django-d...@googlegroups.com.
To unsubscribe from this group, send email to django-develop...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.

[Will Van Wazer]

Despite not being listed on PyPi, installing Django 1.1 works if you do this:

pip install 'Django<1.2'

-------

Will Van Wazer

The Washington Post

(202) 334-9967 (w)
(703) 785-1448 (c)

[David Fischer]

The exact versions of Django available on Pypi are here:

http://pypi.python.org/simple/Django/

Nobody recommends installing this old version of Django for production, but you can install 1.1.4 like so:

pip install django==1.1.4

[Michael Elsdörfer]

I'm only using Django 1.1 as part of CI tests, and they have started failing recently because of this, so I'd be happy to see it fixed.

[Florian Apolloner]

On Friday, December 14, 2012 9:01:27 PM UTC+1, Michael Elsdörfer wrote:

I'm only using Django 1.1 as part of CI tests, and they have started failing recently because of this, so I'd be happy to see it fixed.

I am strongly against showing non-supported versions on PYPI, I also don't see why you'd need 1.1 for CI tests if you don't use it (an nobody should)

[donarb]

On Saturday, December 15, 2012 3:54:10 AM UTC-8, Florian Apolloner wrote:

I am strongly against showing non-supported versions on PYPI, I also don't see why you'd need 1.1 for CI tests if you don't use it (an nobody should)

I disagree. I have a client who is currently running a site with Django 1.0 and a correspondingly old version of Satchmo. In the next few months I intend to upgrade them to at least 1.4 of Django and a compatible version of Satchmo. To do that, I am going to upgrade in steps on the test server, 1.1, 1.2, 1.3, 1.4, testing and rewriting deprecated APIs as I go.

Sure, I have a copy of the repository and can check out tagged versions as I need them, but having specific versions listed in my requirements file makes pip installs much more convenient.

1.1 may not be supported by the Django project team, but developers out here still have to. 

[Jacob Kaplan-Moss]

The point is that you should be using 1.1.4, the latest release in the 1.1 line, and not 1.1.

Jacob

--

You received this message because you are subscribed to the Google Groups "Django developers" group.

To view this discussion on the web visit https://groups.google.com/d/msg/django-developers/-/VgcZ48SXW1QJ.

[Tom Evans]

On Wed, Dec 12, 2012 at 3:56 PM, Michael Elsdörfer <elsdo...@gmail.com> wrote:
> $ pip install django==1.1

If you mean "The most recent point release in the 1.1 family", then
that is "Django>1.1,<1.2"*.
If you mean 1.1.1, then that is "Django==1.1.1"

Cheers

Tom

* If you are using pypi, then "Django<1.2" will do the trick. However,
if you are running your own cheeseshop, you may have imported 1.0.x
and 1.2.x but no 1.1.x - being explicit about the versions you want
avoids confusion.