Reduce clutter in root-level project directory

[GoogleCodeExporter]

Currently, the following must reside in the root-level project directory:

appengine_django/
.google_appengine/
django/

where django/ is a local checkout of the django repo. Why not use a
"common" directory to reduce this clutter? e.g.:

common/
  appengine_django/
  .google_appengine/
  django/

(Note: stolen from http://code.google.com/p/app-engine-patch/ )

Original issue reported on code.google.com by technel@gmail.com on 15 Aug 2008 at 2:27

[GoogleCodeExporter]

I use a "common" application myself for project-specific stuff like middleware I
might not reuse, etc, and that doesn't find a place in my common component 
repository
(laughably called Sabiondo, savior in spanish). I wouldn't like the helper to
*expect* his stuff to be there, since I wouldn't like to clutter my own 
application
for it, and hard coded stuff is bad anyway.

Anyways, three folders shouldn't be called "clutter", IMO.

I'd say, don't make google_appengine rely on being in the project folder, nor on
finding the django folder right there either. It should be a pluggable 
application,
and thus, we should be able to store it elsewhere, as long as the correct 
module path
is in settings.INSTALLED_APPS.

Just brainstorming there. I guess we're talking about changing some hard coded 
stuff
in the core, and then it might be not as easy :)

I'm going to look into it myself (no, I'm not part of the staff :P), and let 
you know
what I have been up to.

Original comment by chris.we...@gmail.com on 19 Aug 2008 at 6:25

[GoogleCodeExporter]

Sorry for double posting :(

I just wanted to say that this kind of stuff would be better placed on a 
development
mailing list. It's not a real issue with the code after all.

Original comment by chris.we...@gmail.com on 19 Aug 2008 at 6:26

[GoogleCodeExporter]

Chris,

Thanks for the reply. Personally, I find having the three extra directories 
quite
annoying. If you project has 14 files/folders in the root directory, that means 
21%
of the directories there are references to packages that I will never edit.

I do agree, though, that there may be a better (more customizable) way to do 
this
than to demand that they be in a common/ directory.

Do give some updates if you come up with anything, Chris!

Original comment by technel@gmail.com on 19 Aug 2008 at 7:17

[GoogleCodeExporter]

The only directory that *must* reside in the top level directory is 
appengine_django,
the other two are only required in certain configurations.

django is only required if you want to use a more specific version of Django 
than is
supplied in the SDK.

.google_appengine is only required if the SDK is not in your python path.

Changing this is not a high priority at the moment. If you want to work up a 
patch to
make the helper operate differently I'll be more than happy to consider it 
though.

Original comment by mattbrow...@gmail.com on 10 Sep 2008 at 4:50

• Added labels: Type-Enhancement, Priority-Low
• Removed labels: Type-Defect, Priority-Medium