that makes sense but as it stands we are importing
```lms.lib.comment_client``` in this module anyway.  we could go in the
other direction, keep using signals, and move the cs user creation method
all the way inside comment client code (somewhere), but i think that could
turn into a rabbit hole.


On Mon, Mar 17, 2014 at 1:03 PM, David Ormsbee <notifications@github.com>wrote:

> In common/djangoapps/student/models.py:
>
> > @@ -40,6 +40,7 @@
> >  from util.query import use_read_replica_if_available
> >
> >  unenroll_done = Signal(providing_args=["course_enrollment"])
> > +user_account_created = Signal(providing_args=["user"])
>
> I believe one of the original motivations was that the student models are
> in common and should therefore not have a dependency on django comment
> client code in LMS.
>
> --
> Reply to this email directly or view it on GitHub<https://github.com/edx/edx-platform/pull/2957/files#r10666346>
> .
>