Re: Django software docs

[Jani Tiainen]

Hi,

What you expect Django to do for you?

Django has been successfully used to write great variety of webapps like 
e-commerce, blogs, cms etc.


So you have to be a bit more spesific what you're looking for.


On 26.09.2016 18:14, Dave Baas wrote:

All,

Can anyone point me to some software documentation, (I work with 3D 
visualization software) that utilizes Django?

Manuals, tutorials, video links and such?

thanks / Dave

--
You received this message because you are subscribed to the Google 
Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send 
an email to django-users+unsubscr...@googlegroups.com 
.
To post to this group, send email to django-users@googlegroups.com 
.

Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/e1bb770a-3b6e-4be2-806f-0e01302d3c7b%40googlegroups.com 
.

For more options, visit https://groups.google.com/d/optout.


--
Jani Tiainen

--
You received this message because you are subscribed to the Google Groups "Django 
users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/024af0bd-bab9-3bb0-8732-cd158965051e%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Repetitve/Infinite migrations generated on ManyToManyField

[Mike Dewhirst]

On 27/09/2016 6:58 AM, Marvin Mednick wrote:
I've the the following models related to a many-to-many 
relationship.   (Django 1.9.4  and sqlite)


Each time I run makemigrations, it generates an AlterField migration, 
which migrate successfully executes (no errors), but running 
makemigrations again will generate the identical migration.


Everything seems to be functional, but it shouldn't be doing this. Â

Any guidance on what is causing this and ow to resolve or workaround this?


Try declaring those constants outside the class. I think the migration 
code sees things differently each time it looks.




Classes:
class BugbaseFilter(models.Model):
    AND = 'AND'
    OR = 'OR'
    NONE = 'NONE'
    ASSOC_TYPE = (
        (AND,"AND of all items"),
        (OR,"OR of all items"),
        (NONE,"Single Item")
    )
    filterName = models.CharField(max_length=50)
    association = 
models.CharField(max_length=4,choices=ASSOC_TYPE,default=AND)



class BugbaseFilterItem(models.Model):
    fieldName   = models.CharField(max_length=100)
    checkValue = models.CharField(max_length=100)
    invert = models.BooleanField(default=False)
    regex = models.BooleanField(default=False)
    bugFilter = models.ManyToManyField(BugbaseFilter, 
related_name='items', related_query_name='item')

    alias = models.CharField(max_length=25, blank=True)

Migration generated:
class Migration(migrations.Migration):

    dependencies = [
        ('BugReporter', '0027_bugbasefilteritem_bugfilter'),
    ]

    operations = [
        migrations.AlterField(
            model_name='bugbasefilteritem',
            name='bugFilter',
           
field=models.ManyToManyField(related_name='items', 
related_query_name='item', to='BugReporter.BugbaseFilter'),

        ),
    ]

The Table that is in my database looks like the following
CREATE TABLE "BugReporter_bugbasefilteritem_bugFilter" ("id" integer 
NOT NULL PRIMARY KEY AUTOINCREMENT, "bugbasefilteritem_id" integer NOT 
NULL REFERENCES "BugReporter_bugbasefilteritem" ("id"), 
"bugbasefilter_id" integer NOT NULL REFERENCES 
"BugReporter_bugbasefilter" ("id"))



FYI... I've tried removing the related_name and related_query_item and 
doesn't make any difference.





--
You received this message because you are subscribed to the Google 
Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send 
an email to django-users+unsubscr...@googlegroups.com 
.
To post to this group, send email to django-users@googlegroups.com 
.

Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/9944f984-22c9-41b0-b592-dcec2a950dd8%40googlegroups.com 
.

For more options, visit https://groups.google.com/d/optout.


--
You received this message because you are subscribed to the Google Groups "Django 
users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/85eb4d1b-9f31-2739-148b-0c99c4e7234a%40dewhirst.com.au.
For more options, visit https://groups.google.com/d/optout.

Repetitve/Infinite migrations generated on ManyToManyField

[Marvin Mednick]

I've the the following models related to a many-to-many relationship.   
(Django 1.9.4  and sqlite)

Each time I run makemigrations, it generates an AlterField migration, which 
migrate successfully executes (no errors), but running makemigrations again 
will generate the identical migration.

Everything seems to be functional, but it shouldn't be doing this.   

Any guidance on what is causing this and ow to resolve or workaround this?

Classes:
class BugbaseFilter(models.Model):
AND = 'AND'
OR = 'OR'
NONE = 'NONE'
ASSOC_TYPE = (
(AND,"AND of all items"), 
(OR,"OR of all items"), 
(NONE,"Single Item")
) 
filterName = models.CharField(max_length=50)
association = 
models.CharField(max_length=4,choices=ASSOC_TYPE,default=AND)


class BugbaseFilterItem(models.Model):
fieldName   = models.CharField(max_length=100)
checkValue = models.CharField(max_length=100)
invert = models.BooleanField(default=False)
regex = models.BooleanField(default=False)
bugFilter = models.ManyToManyField(BugbaseFilter, related_name='items', 
related_query_name='item')
alias = models.CharField(max_length=25, blank=True)

Migration generated:
class Migration(migrations.Migration):

dependencies = [
('BugReporter', '0027_bugbasefilteritem_bugfilter'),
]

operations = [
migrations.AlterField(
model_name='bugbasefilteritem',
name='bugFilter',
field=models.ManyToManyField(related_name='items', 
related_query_name='item', to='BugReporter.BugbaseFilter'),
),
]

The Table that is in my database looks like the following
CREATE TABLE "BugReporter_bugbasefilteritem_bugFilter" ("id" integer NOT 
NULL PRIMARY KEY AUTOINCREMENT, "bugbasefilteritem_id" integer NOT NULL 
REFERENCES "BugReporter_bugbasefilteritem" ("id"), "bugbasefilter_id" 
integer NOT NULL REFERENCES "BugReporter_bugbasefilter" ("id"))


FYI... I've tried removing the related_name and related_query_item and 
doesn't make any difference.




-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/9944f984-22c9-41b0-b592-dcec2a950dd8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Problem with Crispy-Forms

[ludovic coues]

:)

2016-09-26 21:56 GMT+02:00 Jeff Silverman :
> I was able to fumble my way through to the solution.  What I think was
> missing from the TEASER example was to add "CRISPY_TEMPLATE_PACK =
> 'bootstrap3'
> " to the settings.py file.  Once this was added, the radio buttons properly
> displayed under one another.
>
> It was kind of fun picking my way through the users group, which is where I
> found the necessary option.
>
> Thanks much for your assistance.
>
> On Monday, September 26, 2016 at 6:21:49 AM UTC-4, Jeff Silverman wrote:
>>
>> I created an example application using Crispy-Forms.  In forms.py I am
>> using
>>
>> radio_buttons = forms.ChoiceField(
>> choices = (('option_one', 'Option one is this and that be sure to
>> include why it is great'),('option_two', 'Option two can is something else
>> and selecting it will deselect option one')),
>> widget = forms.RadioSelect,
>> initial = 'option_two',
>> )
>>
>> However, when I execute, the two options appear on the same line.  can
>> anyone tell me what I did wrong?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-users+unsubscr...@googlegroups.com.
> To post to this group, send email to django-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/django-users.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/c2e00e9b-7098-4cc7-add5-f14af94bc014%40googlegroups.com.
>
> For more options, visit https://groups.google.com/d/optout.



-- 

Cordialement, Coues Ludovic
+336 148 743 42

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAEuG%2BTbLZL67A6a%2BmubXC1OCfWnRayHAE_NH8sQLw7v3xyrFvA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Problem with Crispy-Forms

[Jeff Silverman]

I was able to fumble my way through to the solution.  What I think was 
missing from the TEASER example was to add "CRISPY_TEMPLATE_PACK = 
'bootstrap3'
" to the settings.py file.  Once this was added, the radio buttons properly 
displayed under one another.  

It was kind of fun picking my way through the users group, which is where I 
found the necessary option.

Thanks much for your assistance.

On Monday, September 26, 2016 at 6:21:49 AM UTC-4, Jeff Silverman wrote:

> I created an example application using Crispy-Forms.  In forms.py I am 
> using 
>
> radio_buttons = forms.ChoiceField(
> choices = (('option_one', 'Option one is this and that be sure to 
> include why it is great'),('option_two', 'Option two can is something else 
> and selecting it will deselect option one')),
> widget = forms.RadioSelect,
> initial = 'option_two',
> )
>
> However, when I execute, the two options appear on the same line.  can 
> anyone tell me what I did wrong?
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/c2e00e9b-7098-4cc7-add5-f14af94bc014%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

django-admin commands, diango 1.10 with python 2 & python 3 on windows installed

[anton]

Hi,

I am using django 1.10.1 with the following configuration:

- windows 7 64bit
- python 2.7.12 32 bit

Now I am switching to python 3 so I installed additionally
python 3.5.2 64 bit.

I still need to keep python 2 because I have
also trac (https://trac.edgewall.org) with mercurial
(https://www.mercurial-scm.org) installed both still needing python2.

Now my question:

 The windows PATH env variable contains python35 and python/scrips
 paths.

 With python 2.7 allone I could call on the console django
 admin-commands like:

>> manage.py showmigrations
or simply
>> manage.py
to see all commands

Now woth both pythons installed
>> manage.py
shows me all commands

But if I try to execute one command like

>> manage.py showmigrations

it does ... nothing, no error ... nothing.

If I call python like

>> python

on the command line the python 3.5.2 shell starts

The only way to make the django-admin commands work
is to call them like this:

>> py -3 manage.py showmigrations

Now it works.
( of course prepending the full python exe path works too
like
 >> c:\python35\python manage.py showmigrations )

Does somebody know the trick to use python 3.5 without the
need to use "py -3"?

Or is a simultanuously installation of python 2 and python 3 on windows
a no-go?

Thanks for a hint

 Anton

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/nsbs5n%24sdk%241%40blaine.gmane.org.
For more options, visit https://groups.google.com/d/optout.

Re: Problem with Crispy-Forms

[ludovic coues]

Do you mind to share your full forms.py file ?
The result in the teaser seems to depend on the FormHelper

2016-09-26 16:19 GMT+02:00 Jeff Silverman :
> Thanks for the explanation.  I think I get it.  Does that, however, explain
> why the Radio buttons don't display on separate lines?  The "teaser" example
> on GITHUB shows the output cleanly space on separate lines.  That's the part
> I don't quite understand.
>
> On Monday, September 26, 2016 at 6:21:49 AM UTC-4, Jeff Silverman wrote:
>>
>> I created an example application using Crispy-Forms.  In forms.py I am
>> using
>>
>> radio_buttons = forms.ChoiceField(
>> choices = (('option_one', 'Option one is this and that be sure to
>> include why it is great'),('option_two', 'Option two can is something else
>> and selecting it will deselect option one')),
>> widget = forms.RadioSelect,
>> initial = 'option_two',
>> )
>>
>> However, when I execute, the two options appear on the same line.  can
>> anyone tell me what I did wrong?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-users+unsubscr...@googlegroups.com.
> To post to this group, send email to django-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/django-users.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/d22d8604-1c11-4d31-9ddb-76b7ab3edd12%40googlegroups.com.
>
> For more options, visit https://groups.google.com/d/optout.



-- 

Cordialement, Coues Ludovic
+336 148 743 42

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAEuG%2BTZ%2Bg-S4GoPsHM5eTSxmtg8_5yfHFiT6_2eQaJme%2BAWpQw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ANNOUNCE] Django security releases issued: 1.9.10 and 1.8.15

[Tim Graham]

Today the Django team issued 1.9.10 and 1.8.15 as part of our security 
process. These releases address a security issue, and we encourage all 
users to upgrade as soon as possible.

Details are available on the Django project weblog:

https://www.djangoproject.com/weblog/2016/sep/26/security-releases/

As a reminder, we ask that potential security issues be reported via 
private email to secur...@djangoproject.com and not via Django's Trac 
instance or the django-developers list. Please see 
https://www.djangoproject.com/security for further information.

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/94b6bfdb-3b5e-459d-8e74-054325ee56f7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Deleting PROTECTED objects that would be deleted by a CASCADE anyway

[Tim Graham]

And now a Trac ticket for this: https://code.djangoproject.com/ticket/27272

On Friday, September 23, 2016 at 7:17:32 AM UTC-4, Daniel Izquierdo wrote:
>
> Hello,
>
> Consider this set of models:
>
> class Artist(models.Model):
> name = models.CharField(max_length=10)
>
> class Album(models.Model):
> artist = models.ForeignKey(Artist, on_delete=models.CASCADE) 
> 
> 
> class Song(models.Model):
> artist = models.ForeignKey(Artist, on_delete=models.CASCADE)
> album = models.ForeignKey(Album, on_delete=models.PROTECT)
>
>
> And the following test:
>
> class TestDeletion(TestCase):
> def test_delete(self):
> artist = Artist.objects.create(name='test')
> album = Album.objects.create(artist=artist)
> Song.objects.create(artist=artist, album=album)
>
> artist.delete()
>
> What is the expected result of the test?
>
> Currently, this test fails with ProtectedError raised, because trying to 
> delete the artist results in trying to delete the album, which is protected 
> because of the related song. But, the related song was going to be deleted 
> anyway, via the cascading relationship to the artist itself. So I believe 
> that in this case, deletion should succeed.
>
> If there's agreement that the current behavior is a bug, I'll open a 
> ticket with a proper test case and work on a fix.
>
> Thanks,
>
> --
> Daniel Izquierdo
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/be34718c-73e1-469d-a81c-1a7e9be79957%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Django software docs

[Dave Baas]

All,

Can anyone point me to some software documentation, (I work with 3D 
visualization software) that utilizes Django?
Manuals, tutorials, video links and such?

thanks / Dave

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/e1bb770a-3b6e-4be2-806f-0e01302d3c7b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Problem with Crispy-Forms

[Jeff Silverman]

Thanks for the explanation.  I think I get it.  Does that, however, explain 
why the Radio buttons don't display on separate lines?  The "teaser" 
example on GITHUB shows the output cleanly space on separate lines.  That's 
the part I don't quite understand.

On Monday, September 26, 2016 at 6:21:49 AM UTC-4, Jeff Silverman wrote:
>
> I created an example application using Crispy-Forms.  In forms.py I am 
> using 
>
> radio_buttons = forms.ChoiceField(
> choices = (('option_one', 'Option one is this and that be sure to 
> include why it is great'),('option_two', 'Option two can is something else 
> and selecting it will deselect option one')),
> widget = forms.RadioSelect,
> initial = 'option_two',
> )
>
> However, when I execute, the two options appear on the same line.  can 
> anyone tell me what I did wrong?
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/d22d8604-1c11-4d31-9ddb-76b7ab3edd12%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Getting AttributeError: type object 'RunPython' has no attribute 'noop' error

[Tim Graham]

RunPython.noop is new in Django 1.8.

You should try to upgrade as 1.7.x is unsupported and has unpatched 
security issues.

On Monday, September 26, 2016 at 7:03:36 AM UTC-4, Arundas R wrote:
>
> My django version is 1.7.11. While migrating I get an error as described. 
> What might be the possible reason?
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/5abb1199-2a2d-46d4-b238-7ac7a7979458%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Problem with Crispy-Forms

[ludovic coues]

I use something like that as a starting template, with bootstrap 4



{% load staticfiles %}



{% block title %}WEBSITE{% endblock %}

{% block head %}
{% endblock %}


  WEBSITE
  

  ABOUT

  SEARCH
  


  {% block header %}
WEBSITE{% endblock %}
  


 {% block body %}
{% endblock %}


The idea is to have your layout in base.html and only fill the block
with your content.



2016-09-26 13:23 GMT+02:00 Jeff Silverman :
> Followup.  I am playing with the teaser application on GITHUB.
>
> One more thing, which may be the problem, and keep in mind I am new to
> DJANGO and Python...  What goes into the base.html file?
>
> On Monday, September 26, 2016 at 6:21:49 AM UTC-4, Jeff Silverman wrote:
>>
>> I created an example application using Crispy-Forms.  In forms.py I am
>> using
>>
>> radio_buttons = forms.ChoiceField(
>> choices = (('option_one', 'Option one is this and that be sure to
>> include why it is great'),('option_two', 'Option two can is something else
>> and selecting it will deselect option one')),
>> widget = forms.RadioSelect,
>> initial = 'option_two',
>> )
>>
>> However, when I execute, the two options appear on the same line.  can
>> anyone tell me what I did wrong?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-users+unsubscr...@googlegroups.com.
> To post to this group, send email to django-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/django-users.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/d7b92aa1-6722-44f9-88fd-e562a4d76045%40googlegroups.com.
>
> For more options, visit https://groups.google.com/d/optout.



-- 

Cordialement, Coues Ludovic
+336 148 743 42

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAEuG%2BTbfk_DrX7zT0NXcXdVp-zocdUakVqRznqZL9VBFbgRDBA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Problem with Crispy-Forms

[Jeff Silverman]

Followup.  I am playing with the teaser application on GITHUB.

One more thing, which may be the problem, and keep in mind I am new to 
DJANGO and Python...  What goes into the base.html file?

On Monday, September 26, 2016 at 6:21:49 AM UTC-4, Jeff Silverman wrote:

> I created an example application using Crispy-Forms.  In forms.py I am 
> using 
>
> radio_buttons = forms.ChoiceField(
> choices = (('option_one', 'Option one is this and that be sure to 
> include why it is great'),('option_two', 'Option two can is something else 
> and selecting it will deselect option one')),
> widget = forms.RadioSelect,
> initial = 'option_two',
> )
>
> However, when I execute, the two options appear on the same line.  can 
> anyone tell me what I did wrong?
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/d7b92aa1-6722-44f9-88fd-e562a4d76045%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Script App Developer

[ludovic coues]

That's exactly the subject of the django girls tutorial

https://tutorial.djangogirls.org/

2016-09-26 11:57 GMT+02:00 Civan Tunc :
> Hi. Can you write a script or application to develop a blog site using
> Django?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-users+unsubscr...@googlegroups.com.
> To post to this group, send email to django-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/django-users.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/a3f278f8-7afc-42f6-8a02-a502e67a834e%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.



-- 

Cordialement, Coues Ludovic
+336 148 743 42

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAEuG%2BTa9gK%2BPpYz7%2BHJ-hMVzGJ6iXAfTpHy3E-Bp5L%2Bg2eKh7A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Script App Developer

[Civan Tunc]

Hi. Can you write a script or application to develop a blog site using 
Django?

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/a3f278f8-7afc-42f6-8a02-a502e67a834e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Getting AttributeError: type object 'RunPython' has no attribute 'noop' error

[Arundas R]

My django version is 1.7.11. While migrating I get an error as described. 
What might be the possible reason?


-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/64a5fe20-7bed-40a6-98cb-8a8360c796e1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Problem with Crispy-Forms

[Jeff Silverman]

I created an example application using Crispy-Forms.  In forms.py I am 
using 

radio_buttons = forms.ChoiceField(
choices = (('option_one', 'Option one is this and that be sure to 
include why it is great'),('option_two', 'Option two can is something else 
and selecting it will deselect option one')),
widget = forms.RadioSelect,
initial = 'option_two',
)

However, when I execute, the two options appear on the same line.  can 
anyone tell me what I did wrong?

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/1b0f6ca4-37f6-4870-9a8e-6030f9436964%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.