Hi Adam,
I was hitting same issue but never got chance to debug it.
If the underneath database support database transactions then isn't that
each test will be treated as a separate transaction and transaction should
be rolled back
after the test is over to keep the database sane ?
On Wednesday,
Hi,
Am trying to write a customized authentication model.
In authenticate function I do the following.
def authenticate(self, username=None, password=None):
try:
# Check if this user is valid on the mail server
s.auth = HttpNtlmAuth(username, password, s)
Hi,
I store some data like email text, headers and from email address in
encoded format in the database.
I want to have a page where I can display all this information in readonly
format.
What is the ideal place & way to decode this information and pass it to
django UI.
I was thinking of
ld put:
>
> https://support.google.com/mail/troubleshooter/1668960?rd=1#ts=1665018%2C1665144
>
>
> El viernes, 5 de febrero de 2016, 2:04:44 (UTC+1), learn django escribió:
>>
>> I tried both but no luck.
>>
>> On Thursday, February 4, 2016 at 3:49:48 PM UTC-8,
e:
>
>> Hello,
>> If you are writing about his project:
>> https://github.com/coddingtonbear/django-mailbox I guess
>> it's better to ask in the issues page of that project:
>> https://github.com/coddingtonbear/django-mailbox/issues
>>
>>
>>
Hi,
Am trying to setup django mailbox from admin page and seeing issues.
My email address is f...@company.com. We use google.com for our email
service.
My username is "a...@company.com", name is "abc abc" and password is
"abc1234".
Am putting following details on django_mailbox page.
Name:
Hi LP.
Your allow_migrate function differs in the format from what is mentioned in
the link below.
https://docs.djangoproject.com/en/dev/topics/db/multi-db/#topics-db-multi-db-routing
I have tried this last week and it works fine.
On Wednesday, December 9, 2015 at 2:47:42 AM UTC-8, Łukasz
'TEST']['NAME'] -- is that intentional?
>
> On Tuesday, December 8, 2015 at 8:30:05 PM UTC-5, learn django wrote:
>>
>> Hi Tim,
>>
>> My test case was working with new app in new project which was
>> using default database.
>>
>> DATABASES = {
>> 'default': {
',
}
}
On Wednesday, December 2, 2015 at 4:18:25 PM UTC-8, learn django wrote:
>
> Will try to send minimal project by end of the day.
> Hopefully I can discover the reason during this exercise.
>
> On Wednesday, December 2, 2015 at 3:33:30 PM UTC-8, Tim Graham wrote:
>>
>>
On Wednesday, December 2, 2015 at 10:48:52 PM UTC-8, Xavier Ordoquy wrote:
>
> Hi,
>
> > Le 3 déc. 2015 à 00:12, learn django <siddhesh...@gmail.com
> > a écrit :
> >
> > My app uses rest framework.
> > I am writing test cases which involve sta
together, you might discover the reason for the
> failure.
>
> On Wednesday, December 2, 2015 at 6:29:07 PM UTC-5, learn django wrote:
>>
>> Below is the test file & logs.
>> No matter in which order (using --reverse) I run the suite it fails.
>> The
test file including imports.
>
> On Wednesday, December 2, 2015 at 11:20:27 AM UTC-5, learn django wrote:
>>
>> Hi Tim,
>>
>> Below is what am trying to achieve.
>>
>> class OrcaTestCase(TestCase):
>>
>> def test_customer_create_modify_delete(self
Hi,
My app uses rest framework.
I am writing test cases which involve standard requests like
GET/POST/DELETE/PUT.
What is the best approach to write the test cases ?
Should I run the web server from unit test in setUp() (by running 'python
manage.py runserver') so that http
request response
13 matches
Mail list logo