Release setup.py doesn't install 'conf'

[GoogleCodeExporter]

If you check out the source and run setup.py install, the `conf` directory
gets installed.

If you make a release of that same source (such as the release published on
this website) and run its setup.py install, the `conf` directory is not
installed.

Original issue reported on code.google.com by kenneth.arnold on 12 May 2009 at 10:57

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

When I do:

$ git clone git://github.com/django-extensions/django-extensions.git 
$ cd django-extensions.git
$ python setup.py sdist
$ cd dist
$ tar xzvf django-extensions-0.4.tar.gz
$ cd django-extensions-0.4
$ python setup.py install --prefix=/tmp/test
$ find /tmp/test |grep conf | wc -l
25

It seems to work for me.
Can you elaborate on this ?

Original comment by v.oostv...@gmail.com on 14 May 2009 at 6:12

[GoogleCodeExporter]

Hm, could it be a problem only with Python 2.6? I just repeated it on a pretty 
much
pristine VM on which I've made a virtualenv:

$ easy_install django-extensions
Searching for django-extensions
Reading http://pypi.python.org/simple/django-extensions/
Reading http://code.google.com/p/django-command-extensions/
Best match: django-extensions 0.4
Downloading
http://django-command-extensions.googlecode.com/files/django-extensions-0.4.tar.
gz
Processing django-extensions-0.4.tar.gz
Running django-extensions-0.4/setup.py -q bdist_egg --dist-dir
/tmp/easy_install-EtmiZU/django-extensions-0.4/egg-dist-tmp-qkJzQD
zip_safe flag not set; analyzing archive contents...
django_extensions.management.utils: module references __file__
...
Adding django-extensions 0.4 to easy-install.pth file

Installed 
/home/kcarnold/py/lib/python2.6/site-packages/django_extensions-0.4-py2.6.egg

And the contents of that directory are:
admin/        __init__.py   jobs/         templatetags/ 
db/           __init__.pyc  management/   utils/        

(no 'conf').

Original comment by kenneth.arnold on 14 May 2009 at 3:39

[GoogleCodeExporter]

Forgot to mention I'm also using Python 2.6 (Ubuntu Jaunty)

I reproduced your problem when using easy_install as well.
It worked fine when using pip...

This definitly needs looking into... but I'm afraid I do not have the time to 
do this
at the moment.

Hopefully somebody else can create a patch... because I'll be busy for the next
couple of weeks...

Temporary work around is either using pip or manually installing.

Original comment by v.oostv...@gmail.com on 14 May 2009 at 4:12

• Changed state: Accepted
• Added labels: Priority-High, easy_install
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Ironically, I noticed the problem first in a pip install (following the Pinax 
devel
setup instructions, so it was Pinax's boot script that ran things), and 
duplicated it
with easy_install and manual install of the release tarball. The workaround for 
me
was using a git clone.

There's some special-casing for conf in setup.py; I don't know what it's doing, 
but
it smells fishy here.

Original comment by kenneth.arnold on 14 May 2009 at 6:13

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Original comment by leidel on 21 May 2009 at 1:23

• Changed state: Fixed

[GoogleCodeExporter]

I've fixed that in http://tinyurl.com/6bc827da. I strongly suggest to make a 
0.4.1 release because of that.

Original comment by leidel on 21 May 2009 at 1:30

[GoogleCodeExporter]

Done, please double check that everything works okey in the new release.

Original comment by v.oostv...@gmail.com on 21 May 2009 at 7:36