[Django] #23119: itertools.tee' object has no attribute '__getitem__' after upgraded to Django 1.7rc2
Django
Django 1.7rc2
-------------------------------+----------------------
Reporter: anonymous | Owner: nobody
Type: Bug | Status: new
Component: Uncategorized | Version: 1.7-rc-2
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+----------------------
I have just installed django 1.7rc2. When trying to run the development
server with manage.py I get the following error:
{{{
TypeError: Error when calling the metaclass bases
'itertools.tee' object has no attribute '__getitem__'
}}}
Full traceback at: https://dpaste.de/8JS9.
Django 1.7rc1 works perfectly well.
--
Ticket URL: <https://code.djangoproject.com/ticket/23119>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Django
Django 1.7rc2
Reporter: anonymous | Owner: nobody
Type: Bug | Status: closed
Component: Uncategorized | Version: 1.7-rc-2
Severity: Normal | Resolution: duplicate
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
Changes (by bmispelon):
* status: new => closed
* needs_better_patch: => 0
* resolution: => duplicate
* needs_tests: => 0
* needs_docs: => 0
Comment:
Hi,
This seems like a duplicate of #23112.
Can you confirm and reopen this ticket if that's not the case?
Thanks.
--
Ticket URL: <https://code.djangoproject.com/ticket/23119#comment:1>
Django
Django 1.7rc2
Reporter: anonymous | Owner: nobody
Type: Bug | Status: new
Component: Uncategorized | Version: 1.7-rc-2
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Easy pickings: 0 | UI/UX: 0
Changes (by anonymous):
* status: closed => new
* resolution: duplicate =>
Comment:
I ran https://github.com/django/django/pull/2990, but the problem is still
there: http://pastebin.com/AX2t7YxT
--
Ticket URL: <https://code.djangoproject.com/ticket/23119#comment:2>
Django
Django 1.7rc2
Reporter: anonymous | Owner: nobody
Type: Bug | Status: new
Component: Uncategorized | Version: 1.7-rc-2
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Easy pickings: 0 | UI/UX: 0
Changes (by lemuelf):
* cc: lemuelf@… (added)
--
Ticket URL: <https://code.djangoproject.com/ticket/23119#comment:3>
Django
Django 1.7rc2
Reporter: anonymous | Owner: nobody
Type: Bug | Status: new
Component: Uncategorized | Version: 1.7-rc-2
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Easy pickings: 0 | UI/UX: 0
Comment (by lemuelf):
I have the same issue (similar traceback as the one in the ticket
description; triggered by the same 3rd party library) but after using the
branch in https://github.com/django/django/pull/2990 the development
server worked for me. Let me know if there's any info I can add.
--
Ticket URL: <https://code.djangoproject.com/ticket/23119#comment:4>
Django
Django 1.7rc2
Reporter: anonymous | Owner: nobody
Type: Bug | Status: new
Component: Uncategorized | Version: 1.7-rc-2
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Easy pickings: 0 | UI/UX: 0
Comment (by CollinAnderson):
Good catch. Your new traceback actually shows a different error
(`IndexError: list index out of range`) that happens if the iterable is
empty, which is fine on 1.6. I've commented on the first ticket.
https://code.djangoproject.com/ticket/23112#comment:16
--
Ticket URL: <https://code.djangoproject.com/ticket/23119#comment:5>
Django
Django 1.7rc2
Reporter: anonymous | Owner: nobody
Type: Bug | Status: new
Component: Uncategorized | Version: 1.7-rc-2
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Easy pickings: 0 | UI/UX: 0
Changes (by CollinAnderson):
* cc: cmawebsite@… (added)
--
Ticket URL: <https://code.djangoproject.com/ticket/23119#comment:6>
Django
-------------------------------+--------------------------------------
Reporter: anonymous | Owner: nobody
Type: Bug | Status: new
Component: Uncategorized | Version: 1.7-rc-2
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Easy pickings: 0 | UI/UX: 0
--
Ticket URL: <https://code.djangoproject.com/ticket/23119#comment:7>
Django
Reporter: anonymous | Owner: nobody
Type: Bug | Status: new
Component: Uncategorized | Version: 1.7-rc-2
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Easy pickings: 0 | UI/UX: 0
Changes (by CollinAnderson):
* severity: Normal => Release blocker
--
Ticket URL: <https://code.djangoproject.com/ticket/23119#comment:8>
Django
---------------------------------+--------------------------------------
Type: Bug | Status: new
Component: Uncategorized | Version: 1.7-rc-2
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Easy pickings: 0 | UI/UX: 0
Changes (by jcuotpc):
* cc: Jcuotpc@… (added)
--
Ticket URL: <https://code.djangoproject.com/ticket/23119#comment:9>
Django
---------------------------------+--------------------------------------
Type: Bug | Status: new
Component: Uncategorized | Version: 1.7-rc-2
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Easy pickings: 0 | UI/UX: 0
Comment (by areski):
See the last commit that solve ticket #23112
(https://github.com/django/django/pull/2990), it should fix this issue
too.
--
Ticket URL: <https://code.djangoproject.com/ticket/23119#comment:10>
Django
---------------------------------+--------------------------------------
Type: Bug | Status: new
Component: Uncategorized | Version: 1.7-rc-2
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Easy pickings: 0 | UI/UX: 0
Changes (by areski):
* cc: areski@… (added)
--
Ticket URL: <https://code.djangoproject.com/ticket/23119#comment:11>
Django
---------------------------------+--------------------------------------
Type: Bug | Status: new
Component: Uncategorized | Version: 1.7-rc-2
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Easy pickings: 0 | UI/UX: 0
Comment (by anonymous):
The last commit that solved ticket #23112 (
https://github.com/django/django/pull/2990) fixed the issue for me, too.
--
Ticket URL: <https://code.djangoproject.com/ticket/23119#comment:12>
Django
---------------------------------+--------------------------------------
Type: Bug | Status: new
Component: Uncategorized | Version: 1.7-rc-2
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Easy pickings: 0 | UI/UX: 0
Comment (by areski):
I think we could close this ticket and mark it as duplicate
--
Ticket URL: <https://code.djangoproject.com/ticket/23119#comment:13>
Django
---------------------------------+--------------------------------------
Type: Bug | Status: closed
Component: Uncategorized | Version: 1.7-rc-2
Severity: Release blocker | Resolution: duplicate
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Easy pickings: 0 | UI/UX: 0
Changes (by CollinAnderson):
* status: new => closed
* resolution: => duplicate
Comment:
I agree.
--
Ticket URL: <https://code.djangoproject.com/ticket/23119#comment:14>