Re: Is it a bad idea to start a project using Django 1.7 at this moment?

Just a general lack of tutorials properly explaining everything I would say. Though I could be wrong as I dont have that much experience. Hosting in general just makes me sick.

On Saturday, January 2, 2016 at 9:01:46 PM UTC+6, Tim Graham wrote:

Yes, it's a bad idea. Django 1.7 is unsupported and no longer receives security updates. Please use at least the Django 1.8 series (the latest is 1.8.8 as of now) which is a long-term support release and will receive security updates until April 2018 as described at https://www.djangoproject.com/download/#supported-versions.

I'd be curious to hear under what circumstances using the latest version of Django will cause headaches for hosting. It really shouldn't affect any hosting providers as far as I know.

On Saturday, January 2, 2016 at 9:53:23 AM UTC-5, Tahmid Khan wrote:

Hey guys, I am starting work on a website and I was thinking if starting with Django 1.7 is a bad idea or not, since 1.9 is out right now. With 1.7, I feel like hosting will be less of a headache.

--
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+unsubscribe@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/4f01d1fc-e154-458b-abdc-ac404381260c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Django i18n design rationale

Hi,

Am Fri, 1 Jan 2016 15:29:16 -0800 (PST)
schrieb Jure Erznožnik <jure.erznoznik@gmail.com>:
> 1. Expressions gathering vs declaring: Django has utilities to gather
> expressions from sources, txt files and also javascript files. While
> that by itself is a design choice, it also presents us with problems
> such as (possibly very) long expression keys, random .po file layout,
> etc. Are there any serious advantages that favor this approach vs
> declarative one?
>
> 2. What's the point of .po / .mo files? Their structure is not really
> far from standard Python code, so why all the work with compilation?

I wasn't around Django at that time, but to mee it seems pretty
clear that those two aren't explicit design decisions made by Django but
instead Django just decided to use gettext[1], the de-facto standard for
internationalization in the Unix world instead of implementing an own
system and both the gathering and the .mo files are old design
decisions of gettext.

Cheers
Raphael

--
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+unsubscribe@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/20160102181247.169dd19e%40kvothe.
For more options, visit https://groups.google.com/d/optout.

Re: Could not parse the remainder template inheritance

And if you like it you should just buy BBEdit from BareBones, been using it for years, it's great.

François

> On Jan 2, 2016, at 11:13 AM, Lee Hinde <leehinde@gmail.com> wrote:
>
> If you're just getting your feet wet and don't want to invest in an editor/IDE just yet, try TextWrangler: http://www.barebones.com/products/textwrangler/ It's free and won't get in your way.
>
>> On Jan 2, 2016, at 8:11 AM, Matthew <mbd1925@gmail.com> wrote:
>>
>> Actually it turned out this works!! My TextEdit app was being finnicky and made me re-write the entire code instead of just the quotation marks. Thanks for the help!
>>
>> On Saturday, January 2, 2016 at 10:52:22 AM UTC-5, Matthew wrote:
>> Hi James,
>>
>> I turned smart quotes off and am still having the error. I wasn't aware that could cause future errors though, so thanks for the heads up!
>>
>> On Saturday, January 2, 2016 at 12:44:22 AM UTC-5, James Schneider wrote:
>>
>> On Jan 1, 2016 8:08 PM, "Matthew" <mbd...@gmail.com> wrote:
>> >
>> > Hi all,
>> >
>> > I'm working through the masteringdjango book, and am struggling in the Templates area.
>> >
>> > I created a base.html base template, and am attempting to include a child template.
>> >
>> > This is the child template:
>> >
>> > {% extends "base.html" %}
>> >
>> > {% block title %}The current time{% endblock %}
>> >
>> > {% block content %}
>> > <p>It is now {{ current_date }}.</p>
>> > {% endblock %}
>> >
>> > When I run the site, I get the following error message:
>> > Could not parse the remainder: '"base.html"' from '"base.html"'
>> >
>> > And it points to the first line of the child template.
>> >
>> > I don't understand what I am doing wrong, please help.
>>
>> Was this template code primarily copied/pasted from an example?
>>
>> Can you try deleting and manually typing new quotes around the base.html reference in your {% extends %} tag?
>>
>> Not sure if it's my email client or not, but those appear to be "smart quotes", which lean left/right, usually automatically inserted by editor applications like MS Word or possible from a translation from text to PDF to make things "pretty".
>>
>> To a computer parser like the Django template system, those are interpreted differently as regular characters rather than quotes, which would explain the parser error you are receiving. Hard to spot, but I've been bit by that type of subtle bug before.
>>
>> -James
>>
>
>
> --
> 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+unsubscribe@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/CE45DD84-98D8-406D-A829-CF0C2B7AB86D%40gmail.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+unsubscribe@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/339C31C4-B7C0-4F23-9E00-0774A432C538%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Could not parse the remainder template inheritance

If you're just getting your feet wet and don't want to invest in an editor/IDE just yet, try TextWrangler: http://www.barebones.com/products/textwrangler/  It's free and won't get in your way.

On Jan 2, 2016, at 8:11 AM, Matthew <mbd1925@gmail.com> wrote:

Actually it turned out this works!! My TextEdit app was being finnicky and made me re-write the entire code instead of just the quotation marks. Thanks for the help!

On Saturday, January 2, 2016 at 10:52:22 AM UTC-5, Matthew wrote:

Hi James,

I turned smart quotes off and am still having the error.  I wasn't aware that could cause future errors though, so thanks for the heads up!

On Saturday, January 2, 2016 at 12:44:22 AM UTC-5, James Schneider wrote:

On Jan 1, 2016 8:08 PM, "Matthew" <mbd...@gmail.com> wrote:
>
> Hi all,
>
> I'm working through the masteringdjango book, and am struggling in the Templates area.
>
> I created a base.html base template, and am attempting to include a child template.
>
> This is the child template:
>
> {% extends "base.html" %}
>
> {% block title %}The current time{% endblock %}
>
> {% block content %}
> <p>It is now {{ current_date }}.</p>
> {% endblock %}
>
> When I run the site, I get the following error message: 
> Could not parse the remainder: '"base.html"' from '"base.html"'
>
> And it points to the first line of the child template.
>
> I don't understand what I am doing wrong, please help.

Was this template code primarily copied/pasted from an example?

Can you try deleting and manually typing new quotes around the base.html reference in your {% extends %} tag?

Not sure if it's my email client or not, but those appear to be "smart quotes", which lean left/right, usually automatically inserted by editor applications like MS Word or possible from a translation from text to PDF to make things "pretty".

To a computer parser like the Django template system, those are interpreted differently as regular characters rather than quotes, which would explain the parser error you are receiving. Hard to spot, but I've been bit by that type of subtle bug before.

-James

Re: Could not parse the remainder template inheritance

Actually it turned out this works!! My TextEdit app was being finnicky and made me re-write the entire code instead of just the quotation marks. Thanks for the help!

On Saturday, January 2, 2016 at 10:52:22 AM UTC-5, Matthew wrote:

Hi James,

I turned smart quotes off and am still having the error.  I wasn't aware that could cause future errors though, so thanks for the heads up!

On Saturday, January 2, 2016 at 12:44:22 AM UTC-5, James Schneider wrote:

On Jan 1, 2016 8:08 PM, "Matthew" <mbd...@gmail.com> wrote:
>
> Hi all,
>
> I'm working through the masteringdjango book, and am struggling in the Templates area.
>
> I created a base.html base template, and am attempting to include a child template.
>
> This is the child template:
>
> {% extends "base.html" %}
>
> {% block title %}The current time{% endblock %}
>
> {% block content %}
> <p>It is now {{ current_date }}.</p>
> {% endblock %}
>
> When I run the site, I get the following error message: 
> Could not parse the remainder: '"base.html"' from '"base.html"'
>
> And it points to the first line of the child template.
>
> I don't understand what I am doing wrong, please help.

Was this template code primarily copied/pasted from an example?

Can you try deleting and manually typing new quotes around the base.html reference in your {% extends %} tag?

Not sure if it's my email client or not, but those appear to be "smart quotes", which lean left/right, usually automatically inserted by editor applications like MS Word or possible from a translation from text to PDF to make things "pretty".

To a computer parser like the Django template system, those are interpreted differently as regular characters rather than quotes, which would explain the parser error you are receiving. Hard to spot, but I've been bit by that type of subtle bug before.

-James

--
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+unsubscribe@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/584fd709-1068-431e-960e-25ba74b7112d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Could not parse the remainder template inheritance

Hi James,

I turned smart quotes off and am still having the error.  I wasn't aware that could cause future errors though, so thanks for the heads up!

On Saturday, January 2, 2016 at 12:44:22 AM UTC-5, James Schneider wrote:

On Jan 1, 2016 8:08 PM, "Matthew" <mbd...@gmail.com> wrote:
>
> Hi all,
>
> I'm working through the masteringdjango book, and am struggling in the Templates area.
>
> I created a base.html base template, and am attempting to include a child template.
>
> This is the child template:
>
> {% extends "base.html" %}
>
> {% block title %}The current time{% endblock %}
>
> {% block content %}
> <p>It is now {{ current_date }}.</p>
> {% endblock %}
>
> When I run the site, I get the following error message: 
> Could not parse the remainder: '"base.html"' from '"base.html"'
>
> And it points to the first line of the child template.
>
> I don't understand what I am doing wrong, please help.

Was this template code primarily copied/pasted from an example?

Can you try deleting and manually typing new quotes around the base.html reference in your {% extends %} tag?

Not sure if it's my email client or not, but those appear to be "smart quotes", which lean left/right, usually automatically inserted by editor applications like MS Word or possible from a translation from text to PDF to make things "pretty".

To a computer parser like the Django template system, those are interpreted differently as regular characters rather than quotes, which would explain the parser error you are receiving. Hard to spot, but I've been bit by that type of subtle bug before.

-James

--
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+unsubscribe@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/c449d909-6411-4c55-985d-fb53f5a87316%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Is it a bad idea to start a project using Django 1.7 at this moment?

Yes, it's a bad idea. Django 1.7 is unsupported and no longer receives security updates. Please use at least the Django 1.8 series (the latest is 1.8.8 as of now) which is a long-term support release and will receive security updates until April 2018 as described at https://www.djangoproject.com/download/#supported-versions.

I'd be curious to hear under what circumstances using the latest version of Django will cause headaches for hosting. It really shouldn't affect any hosting providers as far as I know.

On Saturday, January 2, 2016 at 9:53:23 AM UTC-5, Tahmid Khan wrote:

Hey guys, I am starting work on a website and I was thinking if starting with Django 1.7 is a bad idea or not, since 1.9 is out right now. With 1.7, I feel like hosting will be less of a headache.

--
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+unsubscribe@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/5339c8d8-50e5-4cf2-99e5-c78e9c6df7db%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.