[feature request] configurable path for .mr.developer.cfg

[h3]

Would be nice ..

[fschulze]

Could you state a use case? It's in the same location as the .installed.cfg of buildout and is necessary to find the buildout root among other stuff, so it's not trivial to change at all.

[h3]

I'm working on a development environment for django. It heavily rely on buildout, but conceal most of the complexity from the user. The goal is twofold, first I want to make it easier to develop for django and secondly, I want to lower the entry barrier for non-programmer. With this project I hope to be able to hook a designer on a django project with a minimum effort, without having to teach him things like buildout in depth.

To achieve this I put everything that can be "re-builded", including .installed.cfg, in a hidden directory.

This also makes it easier to svn/git ignore those files since there is only one directory to ignore.

For more information:

https://github.com/h3/django-duke-client http://django-duke-client.readthedocs.org

Sorry the doc is a bit outdated .. RTD seems to be readonly for a couple of days now.

Thanks

[fschulze]

Would it work if you could set an environment variable to tell mr.developer where to find the file? There is no other way to find the buildout root otherwise. The config for buildout doesn't have to be named buildout.cfg, bootstrap.py isn't always there either.

[h3]

Yes, that would work for me

[fschulze]

Can you try this branch? https://github.com/fschulze/mr.developer/tree/configurable-buildout-base

[h3]

I can't get it to work properly .. but I'm not sure I have the right approach to test a branch.

Buildout check on pypi for the latest mr.developper version and finds 1.20. I tried to overwrite the egg and re-run buildout, but it always starts by checking for mr.developper on pypi .. so I tink it doesn't use the branch.

How exactly do you test mr.developper from github instead of pypi ?

[fschulze]

I have mr.developer in my sources list and checked out. Then I just switch to the branch and run buildout. Eating my own dog food :) Alternatively you can clone the git repository somewhere, switch to the branch and add the path to "develop =" in your buildout.

[h3]

OK .. I didn't think that would work.

I managed to make it work, it now shows v 1.21 but I still can't get this feature to work .. but I'm pretty sure it should work.

I tried to put print statement to troubleshoot but there's something strange going on. If I put the print statements in any python file in developer/ I see the debug prints in console when I run buildout.

But if I put the print statements in develop.py I don't see them. It's like if the file is never loaded. Furthermore, every python files gets their .pyc counterparts created EXCEPT develop.py ..

Any idea ?

[h3]

OK, managed to get the file called when I use develop activate <module>.

There's only one problem, now it doesn't find buildout.cfg because it looks in the same directory than .mr.developer.cfg.

What need is to be able to put .mr.developer.cfg in a subdirectory .. like this:

project/
    buildout.cfg
    .build/
        .mr.developer.cfg
        eggs/
        ...