Django 1.8 feature in 1.7.9?

[lois...@polyconseil.fr]

Hi,

I updated one of my project to Django 1.7.9, and a migration was added in `django/contrib/contenttypes/migrations/`, namely `0002_remove_content_type_name.py`.

This migration uses `RunPython.noop`, which my version of Django cannot find. It's specified in the doc that this feature is new in Django 1.8.

Is this a bug?

Thanks!

[Tim Graham]

The 1.7.9 wheel file that was first uploaded to PyPI was corrupted. I uploaded a corrected file about 2 hours after the initial release. Sorry for inconvenience and confusion!

[Ben Cail]

I am seeing the same issue when I try to upgrade my project to 1.7.9...

On Thursday, July 9, 2015 at 7:25:02 AM UTC-4, lois...@polyconseil.fr wrote:

[Karen Tracey]

On Thu, Jul 9, 2015 at 9:17 AM, Tim Graham <timog...@gmail.com> wrote:

The 1.7.9 wheel file that was first uploaded to PyPI was corrupted. I uploaded a corrected file about 2 hours after the initial release. Sorry for inconvenience and confusion!

Any guidance on how to recover from a "cached" corrupted wheel?

e.g.:

Collecting Django<1.8,>=1.7.0
Using cached Django-1.7.9-py2.py3-none-any.whl
Hash of the package https://pypi.python.org/packages/py2.py3/D/Django/Django-1.7.9-py2.py3-none-any.whl#md5=2df76c904... (from https://pypi.python.org/simple/django/) (52358ac5f48fd514d6c4eb9e08830985) doesn't match the expected hash 2df76c904
53477a9d0bb6a1608f0dfa5!
Bad md5 hash for package https://pypi.python.org/packages/py2.py3/D/Django/Django-1.7.9-py2.py3-none-any.whl#md5=2df76c90453477a9d0bb6a1608f0dfa5 (from https://pypi.python.org/simple/django/)

Would it be better in general to replace "bad" versions with new releases with new numbers rather than creating a 2nd differing released version of supposedly the same thing?

[Rebecca Muraya]

I had this error. Pip caches things in a few places, maybe more:

  ~/.pip/

  /tmp/

  ~/.cache/pip/

[Tim Graham]

The consequences of replacing the bad wheel file weren't entirely clear. Knowing what we know now, I guess next time (hopefully there won't be one) I will just roll a new version. If you think I should do that at this point, let me know.

[Luis Zárate]

Maybe you need to uninstall django first, clear pip cache and install again.

pip uninstall django==1.7.9
rm ~/.cache/pip/*        # or wherever it is pip cache folder
pip install django==1.7.9

> --
> You received this message because you are subscribed to the Google Groups "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to django-users...@googlegroups.com.
> To post to this group, send email to django...@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-users.
> To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/9a51a562-7729-400c-88f7-84a827ff88ef%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

--

"La utopía sirve para caminar" Fernando Birri