lib/matplotlib/mpl-data/matplotlibrc is generated at build time by interpolating some fields in matplotlibrc.template.
Since it always get changed, it always shows up as a modified file by svn status. This is only a minor annoyance when working on the trunk. However, when working on a branch with svnmerge, svnmerge won't let me merge from trunk if I have any modified files at all, so every time I want to merge, I have to be sure to revert that file.
Is there any reason not to just remove this file from SVN?
···
--
Michael Droettboom
Operations and Engineering Division
Space Telescope Science Institute
Operated by AURA for NASA
Michael Droettboom wrote:
lib/matplotlib/mpl-data/matplotlibrc is generated at build time by interpolating some fields in matplotlibrc.template.
Since it always get changed, it always shows up as a modified file by svn status. This is only a minor annoyance when working on the trunk. However, when working on a branch with svnmerge, svnmerge won't let me merge from trunk if I have any modified files at all, so every time I want to merge, I have to be sure to revert that file.
Is there any reason not to just remove this file from SVN?
I could not think of any reason, and I did not see any message to the contrary, so I went ahead and removed it.
Eric
Could MANIFEST also be removed? I think it is generated from MANIFEST.in.
Darren
···
On Saturday 08 September 2007 09:08:12 pm Eric Firing wrote:
Michael Droettboom wrote:
> lib/matplotlib/mpl-data/matplotlibrc is generated at build time by
> interpolating some fields in matplotlibrc.template.
>
> Since it always get changed, it always shows up as a modified file by
> svn status. This is only a minor annoyance when working on the trunk.
> However, when working on a branch with svnmerge, svnmerge won't let me
> merge from trunk if I have any modified files at all, so every time I
> want to merge, I have to be sure to revert that file.
>
> Is there any reason not to just remove this file from SVN?
I could not think of any reason, and I did not see any message to the
contrary, so I went ahead and removed it.
Darren Dale wrote:
[...]
Could MANIFEST also be removed? I think it is generated from MANIFEST.in.
It is, but it is not clear to me when or how this occurs. Does distutils do it? MANIFEST seems to have special significance, but I don't know anything about it beyond that.
Eric
It is created when we do "python setup.py sdist". Once it is created, it is
used to create the source archive. There is a short discussion here:
http://docs.python.org/dist/manifest-options.html. I think it is appropriate
to remove it from the archive, I'll go ahead and do it.
Darren
···
On Tuesday 11 September 2007 02:23:49 pm Eric Firing wrote:
Darren Dale wrote:
[...]
> Could MANIFEST also be removed? I think it is generated from MANIFEST.in.
It is, but it is not clear to me when or how this occurs. Does
distutils do it? MANIFEST seems to have special significance, but I
don't know anything about it beyond that.