New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Collection config merging feels backwards #98

Closed
bitprophet opened this Issue Nov 27, 2013 · 0 comments

Comments

Projects
None yet
1 participant
@bitprophet
Member

bitprophet commented Nov 27, 2013

Went to actually use the feature in #89 in an Invocations-using project (new Paramiko docs site, as above) and found...I explicitly set it up to merge inner-out, such that a sub-collection wins in conflicts over outer collections. This seems really backwards and I can't tell why I did it that way.

Specifically, I'm distributing Invocations' docs module, which sets defaults for Sphinx project source/build dirs (docs and docs/_build respectively). Then Paramiko's site tries overriding this to be . and _build. That doesn't work because the 'inner' docs module (added to Paramiko's local tasks module as a sub-collection) is winning right now.

Going to reverse the merge order =/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment