Sure, but you could just `from crum import get_current_request`, with no
additional definition. Nothing outside the module has to know that the
function is coming from `crum`.


On Thu, Oct 3, 2013 at 1:27 PM, chrisndodge <notifications@github.com>wrote:

> In common/lib/xmodule/xmodule/util/django.py:
>
> > @@ -0,0 +1,24 @@
> > +"""
> > +Exposes Django utilities for consumption in the xmodule library
> > +NOTE: This file should only be imported into 'django-safe' code, i.e. known that this code runs int the Django
> > +runtime environment with the djangoapps in common configured to load
> > +"""
> > +
> > +from crum import get_current_request as crum_get_current_request
> > +
> > +def get_current_request():
> > +	"""
> > +	Use the tls middleware utility to get the current request on this thread
>
> Will fix comment.
>
> I wanted to make a single utility python module in lib/xmodule so that
> when we use this functionality elsewhere it does not need to be 'crum'
> aware, which again, is a Django app-tier construct.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/edx/edx-platform/pull/1156/files#r6747819>
> .
>