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.
On Friday, May 2, 2014 12:58:47 PM UTC-4, Fabio Caritas Barrionuevo da Luz wrote: > > it was really a bug > > > apparently solved in > > https://github.com/django/django/commit/d1799233f46c39379fe429a4ece128d96b128006 > > Is it still necessary create a new ticket for this? > > > Em quarta-feira, 30 de abril de 2014 23h35min59s UTC-3, Fabio Caritas > Barrionuevo da Luz escreveu: >> >> 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 >> >> >> >> [1] >> https://github.com/django/django/tree/8f6dff372b174e772920de6d82bd085f1a74eaf2 >> > -- 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 [email protected]. To post to this group, send email to [email protected]. 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/4e7403bf-df1f-4da9-a1d1-202575f52231%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
