Configuration warnings with clean 0.3.2 -> 0.4 upgrade - #2772

So, this is kind of a mess. The generated astropy.cfg on 0.3.2 contains a path to to jquery that is generated at build time -- and it points to a file in the working directory not the install directory. git blame tells me it's my fault, so I have only myself to blame... I think what happened here is that the jquery_url stuff was added to 0.3.2 after the configuration work was done on 0.4, and the two never got reconciled.

So that means that comparing the configuration file for a known past state from astropy 0.3.2 will always fail unless you are running on my machine with exactly my directory structure. 0.3.1 does not have this problem (since it has no jquery_url config option), nor does 0.4.0 (where we start using commented out configuration settings anyway).

The conda recipe further seems to patch the config file to point to the install directory (very good thing, but I wish that had been reported upstream). Does anyone know where the anaconda recipes are available for viewing? conda/conda-recipes only contains a very out-of-date recipe for astropy 0.2.5. The conda recipe for 0.4 shouldn't need to do this, and I'd like to confirm.

The second issue could certainly be related to the first. That warning certainly would appear with a stock astropy 0.3.x config file if the detection that it was unedited failed.

Yuck. It'll be great when we're over this hump with the config system :)

I guess this is good to merge?

I want to release 0.4.1 today so that I can stop hearing about #2749.

On the point of where you can see Anaconda recipes, for packages that I have built myself and put on binstar, the recipe is easily available in the installed environment as $CONDA_ROOT/pkgs/<package_name>/info/recipe/. But this recipe directory is not in the packages installed from the official defaults channel provided by Continuum. I'm not sure why that is the case.

Yeah, I think this is ready.