[ANNOUNCE] Django bugfix releases issued: 1.9.1 and 1.8.8

Details are available on the Django project weblog:

https://www.djangoproject.com/weblog/2016/jan/02/bugfix-releases-issued/

On a related note: Python 3.2 users, please be advised that we've decided to drop support for Python 3.2 in Django 1.8.x at the end of 2016. We won't break things intentionally after that, but we won't test subsequent releases against Python 3.2 either. Upstream support for Python 3.2 ends February 2016 so we don't find much value in providing security updates for a version of Python that could be insecure. To read more about the decision and to let us know if this will be problematic for you, please read the django-developers thread: https://groups.google.com/d/topic/django-developers/eMu5UQpUdWs/discussion.

--
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/20b977e6-1264-4833-b759-079652489534%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

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/d73819b9-d1b5-414a-be50-6efbab347285%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Hire a part-time django developer to build a medical website

I hope it's fine to publish job related post here.

I am hiring a  a part-time django, who can build a medical website from scratch. This website facilitates the interaction between the patients and their relatives.

Requirements: 

(1) Very familiar with Django and BootStrap, >2years experiences.

(2) Good communication skills since we will be working together remotely and online

(3) Good coding style, clean and readable

(4) Can finish the website and get it online in 2 months

Compensation: US $1500 (paid 3 installments based on milestone).

Please send me your CV and demo work to phdggg at gmail dot come

Wei Xiong

--
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/0f46dbda-27b7-49e3-86a9-21b5660c82e6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Could not parse the remainder template inheritance

On Jan 1, 2016 8:08 PM, "Matthew" <mbd1925@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/CA%2Be%2BciWddnZGtqhHaN6Y1U7Mzr8_eKTnXJg7fUemzQSBmJ1EGQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Could not parse the remainder template inheritance

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.

--
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/8cf9330e-3d63-484b-afdf-62a8834e0162%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Im stuck with my WSGI FIle on pythonanywhere.com

Oh man! I spent a couple of hours on this. Absolutely ridiculous! Here is what it fixed for my mezzanine's project:

# Remove any references to your home folder (this can break Mezzanine)
while "." in sys.path:
    sys.path.remove(".")
while "" in sys.path:
    sys.path.remove("")

I am writing a post on this. I was following a tutorial and got stuck on this WSGI issue.


On Monday, May 25, 2015 at 1:54:54 PM UTC-5, Robert librado wrote:

939 :Traceback (most recent call last):  2015-05-25 18:45:19,939 :  File "/bin/user_wsgi_wrapper.py", line 130, in __call__  2015-05-25 18:45:19,939 :    self.error_log_file.logger.exception("Error running WSGI application")  2015-05-25 18:45:19,939 :  File "/usr/lib/python2.7/logging/__init__.py", line 1185, in exception  2015-05-25 18:45:19,940 :    self.error(msg, *args, **kwargs)  2015-05-25 18:45:19,940 :  File "/usr/lib/python2.7/logging/__init__.py", line 1178, in error  2015-05-25 18:45:19,940 :    self._log(ERROR, msg, args, **kwargs)  2015-05-25 18:45:19,940 :  File "/usr/lib/python2.7/logging/__init__.py", line 1270, in _log  2015-05-25 18:45:19,940 :    record = self.makeRecord(self.name, level, fn, lno, msg, args, exc_info, func, extra)  2015-05-25 18:45:19,940 :  File "/usr/lib/python2.7/logging/__init__.py", line 1244, in makeRecord  2015-05-25 18:45:19,941 :    rv = LogRecord(name, level, fn, lno, msg, args, exc_info, func)  2015-05-25 18:45:19,941 :  File "/usr/lib/python2.7/logging/__init__.py", line 284, in __init__  2015-05-25 18:45:19,941 :    self.threadName = threading.current_thread().name  2015-05-25 18:45:19,941 :  File "/usr/lib/python2.7/threading.py", line 1160, in currentThread  2015-05-25 18:45:19,941 :    return _active[_get_ident()]  2015-05-25 18:45:19,941 :  File "/bin/user_wsgi_wrapper.py", line 122, in __call__  2015-05-25 18:45:19,941 :    app_iterator = self.app(environ, start_response)  2015-05-25 18:45:19,941 :  File "/home/pycharm/.virtualenvs/django17/local/lib/python2.7/site-packages/django/core/handlers/wsgi.py", line 168, in __call__  2015-05-25 18:45:19,942 :    self.load_middleware()  2015-05-25 18:45:19,942 :  File "/home/pycharm/.virtualenvs/django17/local/lib/python2.7/site-packages/django/core/handlers/base.py", line 44, in load_middleware  2015-05-25 18:45:19,942 :    mw_class = import_string(middleware_path)  2015-05-25 18:45:19,942 :  File "/home/pycharm/.virtualenvs/django17/local/lib/python2.7/site-packages/django/utils/module_loading.py", line 26, in import_string  2015-05-25 18:45:19,943 :    module = import_module(module_path)  2015-05-25 18:45:19,943 :  File "/usr/lib/python2.7/importlib/__init__.py", line 37, in import_module  2015-05-25 18:45:19,943 :    __import__(name)  2015-05-25 18:45:19,943 :ImportError: No module named security

heres the code:

import os  import sys    # assuming your django settings file is at '/home/MYUSERNAME/MYSITE/settings.py'  path = '/home/pycharm/work'  if path not in sys.path:      sys.path.append(path)    os.environ['DJANGO_SETTINGS_MODULE'] = 'work.settings'  from django.core.wsgi import get_wsgi_application  application = get_wsgi_application()

--
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/a313bd0b-85d5-4167-b81a-e372b76158a0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Django i18n design rationale

I've worked with Django for the past few months. While this - I realize - is not much, so far it has been an extremely pleasant experience. Everything seems to be designed just right and works really nicely out of the box.

So I was that much more surprised when I had to prepare my first app for localization. It's not like anything didn't work - it did - it just didn't FEEL right to me. So in light of everythin else being just right, I'd like to ask the community to set me straight on a few points that I'm having issues with:

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?

3. Why (except for reducing expression count) does javascript code have to be gathered in a special domain? Shouldn't that be up to me to decide whether to stick all expressions into one big file or split them up?

LP,
Jure

--
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/159a7905-149b-42da-930b-83371dc62988%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.