Make template.context usable outside of Django

[Kenneth Arnold]

I needed a data structure exactly like Django's Context object for a project. Unfortunately, the whole module imports settings even though it's only needed in one place. The trivial attached patch moves the import to where it's actually needed.

[mcroydon]

This is a pretty trivial patch that applies cleanly and doesn't cause any test breakage. I'm going to call this ready for checkin but please scold me if you should.

[Alex Gaynor]

Is there any reason to move all the imports inside the function, I think we only need to move the settings import as the issue is not having all of Django on disk, it's using it in the context of a django project.

[mcroydon]

No reason other than they were only being used inside that function and I was trying to reduce imports to fit the use case. Django should already be on his pythonpath if he's importing Context from it thought. Updated patch moves the other imports back to the top.

[mcroydon]

Actually update the diff this time.

[Gary Wilson]

(In [10209]) Fixed #10079 -- Moved settings import inside the function that uses it so that the module can be imported without needing settings, thanks kcarnold and mcroydon.

[Gary Wilson]

(In [10210]) [1.0.X]: Fixed #10079 -- Moved settings import inside the function that uses it so that the module can be imported without needing settings, thanks kcarnold and mcroydon.

Backport of r10209 from trunk.

[Jacob]

Milestone 1.1 deleted