I had some thoughts about what tests to add and how to write them. But
everything lead to the same question: how is it possible to configure
several languages for the tests without hardcoding them into settings.py?
--
You received this message because you are subscribed to the Google Groups
I should have read the whole Stack Overflow thread! It looks like Django
has built in ways of doing it.
https://docs.djangoproject.com/en/1.6/topics/testing/tools/#overriding-settings
--
You received this message because you are subscribed to the Google Groups
Mezzanine Users group.
To
I think you can access the settings module like every other place in the code
base. This example recommends the setup and teardown methods for modifying
settings in unit tests: http://stackoverflow.com/a/913596. Hope that helps :-)
--
You received this message because you are subscribed to
Sounds like a good idea, go for it.
On Sat, May 24, 2014 at 6:19 AM, Josh Cartmell joshcar...@gmail.com wrote:
I think this sounds really cool, I've definitely wanted to do things along
these lines before.
On Fri, May 23, 2014 at 4:08 PM, Ahmad Khayyat akhay...@gmail.com wrote:
Tââ
o
Great post Josh, thanks!
On Sat, May 24, 2014 at 5:17 AM, Josh Cartmell joshcar...@gmail.com wrote:
Hey all, I just wrote up a blog post on how I had Cartridge collect extra
information when particular products were added to a user's cart. I
thought I would share and hope it's helpful for
Here we go:
https://bitbucket.org/stephenmcd/mezzanine/pull-request/62/
Create and send pre_page_move and post_page_move signals.
Any value returned by any receiver of the pre_page_move signal will abort
the move. The value is considered an error message, and will be displayed.
The first
