New issue 686: using new repo as *active* repo doesn't require copying config files https://bitbucket.org/yt_analysis/yt/issue/686/using-new-repo-as-active-repo...

Chris Malone:

Current documentation [here](http://yt-project.org/doc/advanced/developing.html#how-to-get-the-source-cod...) says that to use your forked repo as the *active* repo for development you need to copy the *.cfg files for the default repo to your new repo. This doesn't appear to be strictly necessary as `setup.py develop` seems to find them via ctypes or envars.