inconsistent package naming

[GoogleCodeExporter]

I've downloaded the 0.3 tarball, ran python setup.py install and found
myself with a package called "extensions" in my python path. The
installation instructions in the wiki call it "django_extensions". Either
the instructions need to be updated to reflect the new name, or the package
should be called django_extensions. 

django_extensions is a much nicer name to sit in the PYTHONPATH than the
very generic "extensions" package, IMHO...

Original issue reported on code.google.com by marcus.w...@googlemail.com on 23 Sep 2008 at 7:30

[GoogleCodeExporter]

Ok, looking into the subversion repository, I guess the 0.3 tarball is just 
past its
sell-by date. So ignore this issue please, instead take it as a request to 
repackage
the tarball. Thanks!

Original comment by marcus.w...@googlemail.com on 23 Sep 2008 at 7:32

[GoogleCodeExporter]

The plan is to do another release but we're fixing up a few things first and 
might
refactor some more naming.  Thanks.

Original comment by mtr...@gmail.com on 25 Sep 2008 at 5:41

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Thanks for the report Marcus, and sorry about the confusion.

Indeed the svn is 'right-way-to-go' for Django-1.0 at this moment and the docs
reflect svn, not earlier releases. (Though it might be a good point to start 
having
docs for specific versions like Django has)

On the mailinglist we are currently discussing some additional changes 
alongside the
namechange that's currently in svn to make django_extensions more consistent, 
less
bloated and more 'future-proof'.

I originally wanted to have a new release out fairly quickly after Django 1.0 
but
decided against that to not end up with three releases in a row that all have
different entry points for django-extensions.

At the moment I'm also very busy at work because i have to present my research
findings to colleague's at a short-notice, so i don't have as much time to work 
on
django-extensions as i would like. To make matters worse, I have vacation 
coming up
next month in which i plan to explore more of Japan with friends.

When we have a definite consensus on a more profound structure for 
django-extentions
(as currently discussed on the mailinglist) it shouldn't take much time to 
implement
that and create another release. But somebody needs the time and energy to sit 
down
and do it :-)

Please bare with us for the moment.

Regards,
a currently very tired maintainer,

trbs

(p.s. note-to-self, close this in a few days, when everybody had the time to 
read all
the comments :)

Original comment by v.oostv...@gmail.com on 26 Sep 2008 at 8:25

[GoogleCodeExporter]

I'm glad you left it open else I was going to submit a ticket about the same 
thing :-P.

Original comment by steve.mi...@gmail.com on 1 Oct 2008 at 2:34

[GoogleCodeExporter]

invalidating for now

Original comment by v.oostv...@gmail.com on 6 Feb 2009 at 9:02

• Changed state: Invalid