I started a discussion about testing class-based (generic) views, a couple
of people have pitched in already, thought I'd throw this out there in case
anyone else can help:
http://www.obeythetestinggoat.com/testing-django-class-based-generic-views-None.html
It covers a couple of simple examples
On Friday, October 4, 2013 3:51:30 AM UTC+5:30, david.durham.jr wrote:
>
> I think when they hit the browsers back button, the form will have the
> data they entered previously. When they submit it, since it was
> already submitted previously, you could just make it an edit action,
>
That i
On Friday, October 4, 2013 12:00:47 PM UTC+5:30, dspruell wrote:
>
> On Thu, Oct 3, 2013 at 6:15 AM, graeme >
> wrote:
> > I disagree that breaking the back button is always bad. For example
> suppose
> > you have a series of forms (i.e. a "wizard"):
> >
> > Page 1) fill in form. On POST cr
Man, it is becoming less a reality to get this working. Has anyone found a
solution to this? The whole thing is working just fine except for the
tiny_mce_popup.js file.
--
Systems/Software Engineer
--
You received this message because you are subscribed to the Google Groups
"Django users" gro
Leo,
Finally got it working and was able to display the data in the respective
table as desired. Thank you very much.
I appreciate you patience in helping me understand the 'why' and not just
'how' I should do it in a particular way; and for the advice on Django best
practices. I can't thank yo
You are welcome! I hope you succeed in your work.
Cheers,
Leo
Il 05/ott/2013 22:42 "+Emmanuel" ha scritto:
> Leo,
> Finally got it working and was able to display the data in the respective
> table as desired. Thank you very much.
>
> I appreciate you patience in helping me understand the 'why'
Consider using model factories (you can roll your own) or FactoryBoy
https://factoryboy.readthedocs.org/en/latest/
K
On Friday, October 4, 2013 9:17:51 AM UTC-7, Tianyi Wang wrote:
>
> Yes, it'd be nice to have all the data from the existing database.
> I am aware the loading fixtures way, but
Django isn't doing anything sophisticated here -- it's just printing the
result of Python's datetime.now(). Do you get the same result if you start
a python shell and run:
from datetime import datetime
print datetime.now()
If you do, the problem is at the python level, not the Django level.
One
8 matches
Mail list logo
