error in "makemessages" command on latest django version (1.8dev)

125 views
Skip to first unread message

Fabio Caritas Barrionuevo da Luz

unread,
Apr 30, 2014, 10:35:59 PM4/30/14
to django-d...@googlegroups.com
Hello sorry if this is not the correct place for these questions
I was testing the latest version of Django[1] directly from Github and am having this problem.

In this link you can see all the steps I did to get this error

https://asciinema.org/a/9213

I try:

python manage.py makemessages

Result in this: 

optparse.OptionConflictError: option -e/--extension: conflicting option string(s): -e

That would be a bug or am I doing something wrong


Baptiste Mispelon

unread,
May 1, 2014, 12:32:53 AM5/1/14
to django-d...@googlegroups.com
Hi,

No need for apologies: your message is completely appropriate for this mailing list.

I can reproduce the issue you're describing and it does look like a bug.
It seems to have been introduced by this commit: https://github.com/django/django/commit/0707b824fe77e08ca8b75fcc3738ada694f2a3a6.

Would you mind opening a new ticket for this on https://code.djangoproject.com/newticket?

Thanks!
--
You received this message because you are subscribed to the Google Groups "Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-develop...@googlegroups.com.
To post to this group, send email to django-d...@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/97fc2fcc-4ac7-46dd-aef2-9ab42f5608b0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Fabio Caritas Barrionuevo da Luz

unread,
May 2, 2014, 12:58:47 PM5/2/14
to django-d...@googlegroups.com
it was really a bug


apparently solved in

Is it still necessary create a new ticket for this?

Tim Graham

unread,
May 2, 2014, 1:36:28 PM5/2/14
to django-d...@googlegroups.com
No, a ticket isn't needed since it's already been fixed. Also, since this feature wasn't released, we could have simply reopened the original ticket.
Reply all
Reply to author
Forward
0 new messages