Draft
Conversation
92b2461 to
7419b2e
Compare
910ecac to
3c361ed
Compare
a0e806c to
5510e55
Compare
This change adds a small namespace to configuraton objects that behaves like a dictonary allowing objects to made available to e.g. request handlers. Opt to do this by specialising Configuration rather than changing it directly. The rationale is to preserve a distinction between static parts of the configuration of a dpeloyment, which do no change at runtime, versus e.g. a users locale which would be different for each request though consistent for its duration. Such functionality it needed to support templates without restorting to globals within the current system architecture; only congifuration objects are already threaded through most of the places this would need to be available with the correct semantics of an instance being created wherever it is needed.
This addds the necessary logic both to maintain a store of templates and makiung them available for serving within any page via a new template object type. Make sure there is a separation of the test templates from the mainline stuff by wiring a TEMPLATES section into Configuration and reading the necessary paths via the loaded configuration. Doing so allows both source location and the cache directory to be optionally specified via the main ini file and thus are runtime accessible without hard-coding. Use this facility within the tests to adjust the paths.
Add direct listing functions for pending and accepted peers. Test the creation of the pending_peers file via picklesupp. Do so using a raw comparison of the pending peers file Introduce a pending peers fixture and assert that manage_pending_peers produces what is in it then consume it when testing the pending peers listing function.
* expand template packages up-front in TemplateStore.populated() * template packages is UNPOPULATED by default * back template listing onto back_packages and rejig some The following from original commit was addressed by squashes: template loading and rendering works, but listing templates needs to be restored as does priming ...am most of the way convinced that per-package cache dirs want to be done as part of that preparation process and not a call to os.makedirs() when we do an average "get a template store" call
do this to avoid any changes spilling over - this seemed to be happening with the previous phrasing in the tests though it is not entirely clean to me how it can have happened given how the test support code should be
Allow a value of AUTO for the option which, when read, will construct the necessary path when the configuration is loaded.
this is done to allow operation in an environment without urllib3
5510e55 to
5c27b73
Compare
1b0ef8a to
d94b039
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.