[ANNOUNCE] A new governance model has been adopted for the Django project

For several years, there have been efforts underway to change the way the Django open-source software project is run. This eventually produced a concrete proposal, which then went through discussion, revision, and voting by the Django core team, Django Technical Board, and Django Software

Re: Should a custom user have meta.swappable

On Tue, Dec 17, 2019 at 10:47 PM Mike Dewhirst wrote: > ... and I wonder if my custom user model should have an identical Meta > attibute? > No, The 'swappable' Meta attribute is private/undocumented API; if it were meant to be a thing you needed to set, the documentation would tell you to set

Re: use of migrate command and how to see the tables

On Fri, Jul 19, 2019 at 2:58 AM yasar arafath Kajamydeen wrote: > Thanks for the reply. Please try to solve the error which i shared (screen > shot ). > It is not an error. You have no migrations to apply, so the migrate command is telling you it sees nothing to do. It may help you to read the

Re: How to remove a model definition completely in Django when it previously had foreign keys

When you need to remove any piece of code that's been referenced in migrations, generally there's a multi-step process. For sake of a simple example, let's assume you have Model A in App A, and Model B in App B. And at some point you added a foreign key from Model A to Model B, but now you want

Re: Password Policy Adherence. Cannot use the passwords used before

I'm going to suggest you step back and consider whether the policies you want to implement are good policies. A good, solidly-researched set of recommendations is NIST SP800-63B: https://pages.nist.gov/800-63-3/sp800-63b.html In particular, NIST suggests the following: * Do not use a policy

Re: Poor Performance for Form Rendering In Django 1.11

On Mon, Dec 10, 2018 at 6:29 AM John Lehmann wrote: > So my takeaway from what you are saying is that no one is running a > production site with a Django select field to render a country or currency > option (e.g., django-countries or django-money), because either of these > would have well over

Re: Poor Performance for Form Rendering In Django 1.11

On Mon, Dec 10, 2018 at 5:31 AM John Lehmann wrote: > I am still hoping however for someone to explain to me why the default > renderer cannot handle my use case, such as that a few hundred inputs is > too many, or that I am doing something else improperly. Surely this kind > of a change would

Re: Django Code distribution to customers.

Have them sign licensing agreements that force them to pay you lots and lots of money if they copy your code. Seriously, this is the kind of problem you solve with lawyers, not with code. On Tue, Oct 9, 2018 at 10:10 PM vineeth sagar wrote: > We deploy our web applications on the

Re: Template.render(Context) in django 1.10+

On Mon, Mar 12, 2018 at 5:44 PM, Craig de Stigter < craig.destig...@koordinates.com> wrote: > Thanks for the reply. > > So I guess there are actually now two types of templates, and they have > incompatible API. Neither is deprecated. > > Has this confused anyone else? Is this a

Re: Making an object unsaveable ...

The only way to guarantee a model is unsaveable is to do it at the database permission level. You can override methods on the model in your Python code to make it *harder* to save, but you can't make it impossible, because of how Python works. Consider the following simplified pair of classes:

Re: Upgrading from 1.1 to 2.0

https://docs.djangoproject.com/en/2.0/releases/2.0/#miscellaneous See the first item listed there. -- 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

Re: Issues with french accents

JSON is a subset of JavaScript's object-literal syntax. In JavaScript, as in Python 3, string literals are defined to be Unicode. JSON is defined as specifically using UTF-8 as its encoding of Unicode. However, not all systems can handle Unicode passing through them. Luckily, JavaScript, like

Re: Native JIT compiler for Django?

You have not really provided an argument, though. Programmers generally do not just do a thing for the sake of doing the thing, even if it's a "neat" thing. They do a thing because they have a need for that thing. We turn to things that can speed up our programs once we have determined that some

Re: django 2 under python 2

You should be seeing a message like this: == Unsupported Python version == This version of Django requires Python 3.4, but you're trying to install it on Python 2.7. This may be because you are using a version of pip that

Re: unique_together does not work in django 2.0

You've indented the 'Meta' declaration too much, and Python thinks it's part of the '__str__()' method of your class. Un-indent it one level. On Thu, Jan 18, 2018 at 4:28 PM, FernandoJMM wrote: > Hello, > I have the following class: > >

Re: Is CSRF middleware to be taken seriously (from a XSRF point of view)?

If you can demonstrate a practical attack against Django's CSRF system, feel free to email it to secur...@djangoproject.com. On Tue, Jan 16, 2018 at 1:26 AM, Etienne Robillard wrote: > Hi Stephan, > > I'm also interested to understand why I should have some form of CSRF >

Re: Is CSRF middleware to be taken seriously (from a XSRF point of view)?

The base CSRF secret is per-user, not global. So while you could write a script to hit a page over and over and harvest CSRF tokens, those tokens would only be valid for the session/user associated with your script. Attempting to use them to execute a CSRF attack against another user would fail

Re: 'module' object has no attribute 'lru_cache'

On Wed, Dec 27, 2017 at 2:18 AM, Etienne Robillard wrote: > OK, I've read the INSTALL file and noticed that Django dropped support for > Python 2.7. > > Any reasons for dropping support for Python 2.7 in the first place ? > Python 2.7 reaches its end-of-life (in terms of

Re: utf-8' codec can't decode byte 0x93 in position 31 even though i use read().decode('utf-8') when i read a UploadedFile i get from a file selector in a View in django

The issue you're running into is that the sequence of bytes you passed in is not UTF-8, but you're trying to decode it as UTF-8. The character 'ô' -- that's U+00F4 LATIN SMALL LETTER O WITH CIRCUMFLEX -- is 0xC3 0xB4 in UTF-8. And the byte 0x93 can never be valid as the beginning of a

Re: Python 2 versus 3

Here is a very comprehensive article on why Python 3 is an improvement over Python 2: https://eev.ee/blog/2016/07/31/python-faq-why-should-i-use-python-3/ -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop

Re: A lot of Problems with Migrating (conceptual)

On Thu, Aug 17, 2017 at 1:03 PM, Antonis Christofides < anto...@djangodeployment.com> wrote: > Second, just to make things clear, the word "migration" has two meanings. > The original meaning of migration is to switch to another software system > (e.g. migrate from MySQL to PostgreSQL, or migrate

Re: failed of installing MySLQ

Personally I'd go with SQLite first. Every additional thing you require someone to learn up-front is another obstacle in their path; they can learn how ot manage MySQL or PostgreSQL later on, but first they need to be able to learn about Django. -- You received this message because you are

Re: What Way is best to extend User in Django 1.11?

If the fields you're adding are things that you need to know for purposes of figuring out who someone is and what they're allowed to do, put them in a custom User model. If the fields you're adding are not for the purpose of figuring out who someone is and what they're allowed to do, put them in

Re: View Function Signature?

On Sun, May 14, 2017 at 1:36 PM, Nick Gilmour wrote: > Definition of url: > > *def url(regex, view, kwargs=None, name=None):* > > I also found this: > *def view(request, *args, **kwargs):* > > Neither one of these is what was being asked for. And like several people have

Re: php

Please remember that Django's Code of Conduct applies here, and asks all of us to be respectful of each other and constructive in disagreement. Insulting a person's choice of programming language falls very much on the wrong side of that. As to the original question, there are people who've

Re: Will function based views ever be deprecated?

If you're asking "Will there ever be a point when all built-in views in Django are class-based", the answer is "maybe", because whether to write one of those class-based or function-based depends on what the view needs to do, how much configurability/extensibility it needs to support, etc. If

Re: Django Produces Python?

Python is a programming language. You can use it to write many types of programs. For example, you can use it to write web applications (which run on a web server, respond to HTTP requests, store their data in a database, render HTML templates for output, etc.). But doing this from scratch would

Re: Django queryset High CPU Usage

If all you need is to export data from your database (with or without transforming it along the way) to a CSV, using the normal QuerySet methods is probably the wrong approach; you don't need model objects to do that. Some options include: * Use raw SQL to query for the data and push it to CSV

Re: SESSION_EXPIRE_AT_BROWSER_CLOSE

Make sure you're not looking at users who already had a session cookie set before you changed the setting. Existing cookies might not get immediately rewritten to have the shorter expiration. -- You received this message because you are subscribed to the Google Groups "Django users" group. To

Re: User model not using persistent DB connection?

See the documentation for details: https://docs.djangoproject.com/en/1.10/ref/settings/#conn-max-age Also, generally speaking maintaining a connection pool has been seen as out of scope for Django itself, and most people use a standalone connection pooler (such as pgpool for Postgres). On Thu,

Re: What is the best combination of components to be used with Django on Windows 10?

On Mon, Dec 26, 2016 at 1:31 AM, Avraham Serour wrote: > http://lmgtfy.com/?q=django+deploy+iis > > This is a rude and dismissive way to respond to someone who asked a question; please do not do this in the future, and for further information check out the Django community's

Re: Model _meta API

I'd be against it. At work I deal with one codebase that's Django and one that's Flask/SQLAlchemy, so I've run into the issue of not being able to name a column 'metadata' in a SQLAlchemy ORM model (that name is reserved for SQLAlchemy's internal use, but not underscore-prefixed), and been

Re: user object not available in template

Ah, never mind, misread the question. Are you sure you're using a RequestContext? On Fri, Nov 25, 2016 at 3:23 PM, James Bennett <ubernost...@gmail.com> wrote: > The auth context processor provides it, but not as a variable named > 'user'; instead it's attached to the 'request'

Re: user object not available in template

The auth context processor provides it, but not as a variable named 'user'; instead it's attached to the 'request' variable, so what you want is '{% if request.user.is_authenticated }}'. On Fri, Nov 25, 2016 at 3:02 PM, Drew Ferguson wrote: > Hi > > Using Django 1.10 > > In

Re: What is meaning of '[::1]'?

It's the IPv6 loopback address. So it has the same function as 127.0.0.1, just for IPv6 instead of IPv4. On Sun, Nov 20, 2016 at 6:45 PM, bob gailer wrote: > From https://docs.djangoproject.com/en/1.10/ref/settings/#std:set > ting-ALLOWED_HOSTS: > > "When DEBUG is |True| and

Re: Why was Roberto Rosario silently removed from the Django Software Foundation?

*puts on DSF Director hat* Hi, The Board of Directors of the Django Software Foundation is unaware of any "expulsion" or similar action taken against the person you've named. It seems likely that you, or whomever told you of it, have been misinformed. *takes off DSF Director hat* -- You

Re: How will I Run the Django Project (https://github.com/django/django) in my laptop ?

art of django. How will i assign tickets > to myself ?. How will i run the github django project ? To support the > django community. > > On Sunday, October 30, 2016 at 5:50:30 PM UTC+5:30, James Bennett wrote: >> >> To install and run Django, I recommend reading through th

Re: How will I Run the Django Project (https://github.com/django/django) in my laptop ?

To install and run Django, I recommend reading through the official Django tutorial, which explains how to install Django and create a project you can work with and run: https://docs.djangoproject.com/en/1.10/intro/ Additionally, there is documentation on how to contribute to Django, which is

Re: Django 1.9 Apps aren't loaded yet

On Mon, Apr 25, 2016 at 8:13 AM, wrote: > The initialization process of models seems to be good step in cleaning > many problems, but I don't understant why I can't import models. > The usage of the model should raise exception when it is not > loaded/initialized, but

Re: DjangoCon US 2016

>From reading the CfP page I don't see much of a change; as far as I know with DjangoCon (and PyCon) it's always been the case that, as long as there was a financial aid program, speakers could make use of it, and I believe one or the other or both have prioritized speakers to ensure that getting

Re: Forms in Django

First of all, notice the suggestion was to make the change on your *form* class, not the model -- forms are where you can specify that a particular widget + attributes should be used on a particular field. Though it's also possible to do things in the template itself if you know your way around

Re: How to know our Django version

Django does not have a "featured news" section. Django is not a content-management system; it's a framework for developing many types of Web applications, including content-management systems. It's likely that you were looking at a tutorial for something else that was built using Django. On Thu,

Re: How to know our Django version

As long as you have access to a shell, you can do python manage.py shell Then in the interpreter, do import django print(django.get_version()) On Tue, Feb 2, 2016 at 6:59 AM, wrote: > Hello all, > > thanks in advance for your help. > > i'm just integrating

Re: Hi

To maintain different virtualenvs with different Python versions, I use pyenv: https://github.com/yyuu/pyenv On Sat, Oct 3, 2015 at 7:41 PM, Cristiana Costa wrote: > How can I install the Python 3.5 just in my virtualenv? > > -- > You received this message because you

Re: Possible bug in 1.8 admin app for foreign key handling.

Have you tried setting "required=False" in your custom field override? On Wed, Aug 5, 2015 at 3:23 PM, Scott Gibson wrote: > The django admin app is requiring a foreign key to be populated even > though the model is defined and migrated with null=true and blank=true. > >

Re: Django 1.8 Transaction Begin

As the documentation states, the default behavior in Django is "autocommit", relying on the database's autocommit behavior. This means Django does not need to issue explicit BEGIN and COMMIT statements, so by default Django does not issue them unless the ORM determines that a requested operation

Re: Software Version for MySql that works with django 1.8

Have you read Django's documentation? https://docs.djangoproject.com/en/1.8/ref/databases/#mysql-notes -- 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

Re: QueryDict and its .dict() method - why does it do that?

On Sat, Mar 28, 2015 at 5:37 AM, Stephen J. Butler wrote: > Let's be accurate here: what PHP, Rails, jQuery, et al. do is not > "non-standard". There's nothing wrong with their key-value pairs in > the query string. This is further illustrated by the fact that no >

Re: Django 1.6's lifespan for security updates?

On Wed, Mar 11, 2015 at 3:54 PM, Tim Graham wrote: > Having managed the last few security releases for Django, I'll say it's > one of my least favorite tasks and I'm quite looking forward to dropping > support for 1.4 (which supports Python 2.5) and 1.6 (Python 2.6). But,

Re: How to check if user is already in user database?

This may be a good time to review Django's documentation on how to perform database queries: https://docs.djangoproject.com/en/1.7/topics/db/queries/#retrieving-a-single-object-with-get -- You received this message because you are subscribed to the Google Groups "Django users" group. To

Re: do migrations (Django 1.7+) handle production data?

On Wed, Jan 14, 2015 at 6:34 AM, Abraham Varricatt < abraham.varric...@googlemail.com> wrote: To be more specific, the document you link clearly mentions that "Django > can’t automatically generate data migrations for you" > > > And this is what puzzles me. If it isn't automated and is something

Re: Newbie: How to implement a app/module, which I can include from my html?

The usual way would be to write a custom template tag that fetches the objects and puts them into the template context. -- 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

[ANNOUNCE] Bugfix releases issued

The first bugfix release in the 1.7 series is out, along with bugfix releases for the supported 1.4 and 1.6 release series, and what will hopefully be the final release of the 1.5 series, which is now past end-of-life. Full details are available on the Django project weblog:

Re: What is *the* django 1.7 IDE which is opensource & multiplattform

On Wed, Sep 24, 2014 at 7:17 AM, Bill Freeman wrote: > I just use emacs. > I use Emacs as well. It's been my everyday code editor for nearly 15 years, and works with/on almost anything. -- You received this message because you are subscribed to the Google Groups "Django

Re: Possible bug introduced in Django 1.7 admin/docs?

Are you using any third-party libraries which were installed as eggs? -- 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.

Re: LIMIT 21 on primary key lookups

On Sun, Sep 14, 2014 at 12:48 PM, Ben Collier wrote: > So why 21, precisely? > I can't find the exact changeset in which it was introduced, but I do remember why :) There was an incident involving a large Django installation at World Online, where we were attempting to

[ANNOUNCE] Django 1.7 released

Django 1.7 is now available: https://www.djangoproject.com/weblog/2014/sep/02/release-17-final/ Alongside this are bugfix releases for 1.4, 1.5 and 1.6. The bugfix 1.5 release is the final releae in the 1.5 series, as Django 1.5 has now reached end-of-life. -- You received this message because

Re: Concern about FastCGI deprecation

On Tue, Sep 2, 2014 at 3:08 PM, Javier Guerra Giraldez wrote: > FastCGI isn't a Django concern, as it is a WSGI-only framework (like > most Python frameworks). flup used to be a reasonable FastCGI WSGI > container, but it's no longer supported, so it's unreasonable to ask >

[ANNOUNCE] Django security releases issued

Today we've issued releases to address four security issues reported to us. Full disclosure is on the djangoproject.com weblog: https://www.djangoproject.com/weblog/2014/aug/20/security/ All users are encouraged to upgrade. Additionally, for anyone who missed it, last week we published an

Re: Admin options are just ignored

It is there in the documentation. The first instance just uses "admin.site.register(Poll)" because it hasn't yet begun customizing. Once it starts explaining customization, it tells you, in that section: https://docs.djangoproject.com/en/1.6/intro/tutorial02/#customize-the-admin-form to change

[ANNOUNCE] Django 1.7 RC 2 released

Check out the weblog for details (including information on a change to the keys used to sign Django releases): https://www.djangoproject.com/weblog/2014/jul/27/17rc2/ -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this

Re: [ANNOUNCE] Django 1.7 release candidate 1

On Fri, Jun 27, 2014 at 3:12 AM, cercatrova2 wrote: > "FastCGI support via the runfcgi management command will be removed in > Django 1.9. Please deploy your project using WSGI." > > Why does the documentation *persist* in confusing FastCGI with WSGI? > This does not

[ANNOUNCE] Django 1.7 release candidate 1

We're closing in on the final Django 1.7 release, so it's release-candidate time! Details are up on the Django project blog: https://www.djangoproject.com/weblog/2014/jun/26/17rc1/ -- You received this message because you are subscribed to the Google Groups "Django users" group. To

Re: Language code issue - Django thinks default is en-us?

On Wed, Jun 18, 2014 at 10:21 AM, Stodge wrote: > Even when I override the language code in my custom command get_language() > still returns "en-us". Weird. Guess I'll have to use settings.LANGUAGE_CODE > instead of get_language(). > Define what you mean by "override the

Re: assertXMLEqual behaviour

As far as I can tell from reading the source, there's no deliberate intention one way or another. However, from a strict/pedantic point of view, the example you give is demonstrating correct behavior; due to whitespace, the second document contains nodes not present in the first one. -- You

[ANNOUNCE] Django security releases issued

Today we've issued releases to remedy three security issues reported to us. Affected versions are Django 1.4, Django 1.5, Django 1.6 and the Django 1.7 beta. Full details and download information are on the Django project weblog: https://www.djangoproject.com/weblog/2014/apr/21/security/ --

[ANNOUNCE] Django 1.7 beta 1 released

We're getting closer to 1.7! Details in the blog post here: https://www.djangoproject.com/weblog/2014/mar/20/django-17b1/ -- 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

Re: Is there a good reason why Django querysets can't be intersected?

QuerySets have supported the '&' operator (as measured by implementing the __and__() method) for as long as they've been in Django; the implementation dates all the way back to 0.95. -- You received this message because you are subscribed to the Google Groups "Django users" group. To

Re: Exiting from a management command with a given exit status

On Fri, Jan 24, 2014 at 2:10 AM, Johannes Schneider < johannes.schnei...@galileo-press.de> wrote: > thnx, > I thought there might be a more django-like way. Using standard features of Python and its built-in libraries *is* the "Django-like way". -- You received this message because you are

[ANNOUNCE] Django 1.7 alpha 1 released

Yup, we're on the way to 1.7! Check out the blog post (which mentions a couple of important issues to be aware of *before* trying out the alpha): https://www.djangoproject.com/weblog/2014/jan/22/django-17-alpha-1-released/ And the in-progress 1.7 release notes for a full rundown of what's going

Re: onetoone field and memory issue

https://docs.djangoproject.com/en/1.6/ref/contrib/admin/#django.contrib.admin.ModelAdmin.raw_id_fields -- 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

[ANNOUNCE] Django 1.6 and Django 1.4.10 released

Django 1.6 and Django 1.4.10 are out today; the latter is a bugfix release to restore Python 2.5 compatibility in the 1.4 series. Full details are in the blog post: https://www.djangoproject.com/weblog/2013/nov/06/django-16-released/ -- You received this message because you are subscribed to

[ANNOUNCE] Django 1.4.9 and Django 1.5.5 released

These are minor bugfix releases, so not particularly urgent to upgrade. Details and release notes are available from the blog post: https://www.djangoproject.com/weblog/2013/oct/24/bugfix-releases/ -- You received this message because you are subscribed to the Google Groups "Django users"

[ANNOUNCE] Django 1.6 release candidate available

It's almost here! Tonight we've issued a release candidate for Django 1.6. Information, including links to downloads and release notes, is available on the Django project blog: https://www.djangoproject.com/weblog/2013/oct/22/16c1/ -- You received this message because you are subscribed to the

[ANNOUNCE] Security releases issued -- vulnerability in the wild

Earlier today a message posted to the django-developers mailing list publicly disclosed what was later determined to be an exploitable security issue in Django. As such, we have short-circuited our normal one-week process and moved to immediately issuing new releases to remedy the problem. Full

[ANNOUNCE] Security releases issued (1.4.7, 1.5.3, 1.6 beta 3)

Today the Django team is issuing multiple releases -- Django 1.4.7, Django 1.5.3, and Django 1.6 beta 3 -- as part of our security process. These releases address a directory-traversal vulnerability in one of Django's built-in template tags. More details can be found on our blog:

Re: Exception Value: global name 'dictfetchall2' is not defined

You wrote a method on a class, but didn't define it as taking the 'self' argument that's required for instance methods of Python classes. It may be best to back up a bit and work through some introductory Python tutorials before resuming on your Django app. -- You received this message because

Re: Registration module in 1.5.1 use of django.views.generic.simple

Check out the latest hg tip of django-registration, which does not have this problem. -- 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

Re: Django-Registration/Custom Authentication Issue

Current hg tip is actually 1.5-compatible, in the sense that if you want to use your own User model, you just subclass the provided stuff and plug in your model, either importing directly or using the helper function in Django 1.5. django-registration does not do this itself because 1. Using

Re: django-admin.py startproject mysite

The tutorial mentions the most common issues: * django-admin.py not on your path * django-admin.py lacking executable permission * django-admin.py was renamed by your operating system distributor It also explains how to solve each of those issues. Have you tried the suggested solutions the

Re: make_template_fragment_key is in what version?

Notice that your URL marks the version of Django as 'dev' -- that means it's the documentation for the next, and as-yet-unreleased, version of Django, which will be 1.6. For the documentation for 1.5, change 'dev' in the URL to '1.5' (which is also what will happen when you click the

Re: django-registration vs Django 1.5

I plan to work on it at the PyCon sprints. Rejected some pull requests lately though due to people abusing various features of bitbucket to spam rather than to help, and my policy is not to reward that kind of behavior. -- You received this message because you are subscribed to the Google Groups

ANNOUNCE: Django 1.5 released

Yup, it's finally here! * Announcement blog post here: https://www.djangoproject.com/weblog/2013/feb/26/15/ * Release notes here: https://docs.djangoproject.com/en/1.5/releases/1.5/ * Download it here: https://www.djangoproject.com/download/ -- You received this message because you are

ANNOUNCE: Django 1.5 release candidate 2, Django 1.4.4, Django 1.3.6 (security releases)

We've issued several security releases today. Details are in the blog post: https://www.djangoproject.com/weblog/2013/feb/19/security/ We recommend everyone carefully read this one, as it has an end-user-visible change requiring action beyond simply upgrading your Django package. -- You

[ANNOUNCE] Django 1.5 release candidate available

1.5 is almost here! Today marks the release candidate, which you can read about on the weblog: https://www.djangoproject.com/weblog/2013/jan/04/15-rc-1/ Assuming no release-blocking bugs, Django 1.5 will be released next week. -- You received this message because you are subscribed to the

[ANNOUNCE] Security releases (Django 1.3.5, Django 1.4.3, Django 1.5 beta 2)

Django 1.3.5, Django 1.4.3 and Django 1.5 beta 2 have just been issued in response to security issues. Details are available here: https://www.djangoproject.com/weblog/2012/dec/10/security/ -- You received this message because you are subscribed to the Google Groups "Django users" group. To

[ANNOUNCE] Django 1.5 beta 1 released

Our second milestone on the road to Django 1.5 came today, with the release of the first beta package. Blog post about it is here: https://www.djangoproject.com/weblog/2012/nov/27/15-beta-1/ Release notes are here: https://docs.djangoproject.com/en/dev/releases/1.5-beta-1/ And you can get the

[ANNOUNCE] Django 1.5 alpha 1 released

Our first milestone on the road to Django 1.5 came today, with the release of the first alpha package. Blog post about it is here: https://www.djangoproject.com/weblog/2012/oct/25/15-alpha-1/ Release notes are here: https://docs.djangoproject.com/en/dev/releases/1.5-alpha-1/ And you can get

[ANN] Django 1.4.2 and 1.3.4 remedy security issues

Django 1.4.2 and 1.3.4 have just been released in response to a security issue reported to us. Details are here: https://www.djangoproject.com/weblog/2012/oct/17/security/ Everyone is encouraged to upgrade. -- You received this message because you are subscribed to the Google Groups "Django

Re: Problems with simple "hello world" test - "ImportError: Could not import settings"

On Thu, Sep 13, 2012 at 4:25 AM, DJ-Tom wrote: > Basically I always try to have the same environment for development as I > also use for actual production - I'm lucky that my projects are small enough > so i can do that :-) to avoid last minute surprises when trying to

[ANN] Django 1.3 bugfix release

Today we've issued Django 1.3.3, a quick bugfix release which restores Python 2.4 compatibility in the Django 1.3 release series: https://www.djangoproject.com/weblog/2012/aug/01/django-13-bugfix-release/ Affected users are encouraged to upgrade. -- You received this message because you are

Re: Error in Brand New Django 1.4.1 released Yesterday

On Tue, Jul 31, 2012 at 2:42 AM, JJ Zolper wrote: > What about if you download it from the link I put. When I said "I downloaded a copy of the 1.4.1 tarball", that's exactly what I meant. django.get_version() prints '1.4.1'. I do not know what the problem is with your

Re: Error in Brand New Django 1.4.1 released Yesterday

On Tue, Jul 31, 2012 at 2:15 AM, JJ Zolper wrote: import django print django.get_version() > > I didn't see 1.4.1 I saw 1.5 > > Sure it's probably a minor configuration fix to change it to 1.4.1 but I was > really worried that I did something wrong. > > Maybe

[ANN] Security releases issued, please upgrade ASAP

Today we've issued several releases to remedy security problems reported to the Django team. Details are here: https://www.djangoproject.com/weblog/2012/jul/30/security-releases-issued/ All users are encouraged to upgrade immediately. -- You received this message because you are subscribed to

ANNOUNCE: Django 1.4 released

Django 1.4 is finally here! For details, checkout the weblog: https://www.djangoproject.com/weblog/2012/mar/23/14/ And the release notes: https://docs.djangoproject.com/en/dev/releases/1.4/ -- You received this message because you are subscribed to the Google Groups "Django users" group. To

Re: Will Django run on z/linux?

On Fri, Mar 16, 2012 at 12:06 PM, jc wrote: > We have a number of z/linux (z/vm s390) Linux servers and would like > to consider porting this application to one of the instances.  Will it > run on z? For Django to run on a platform, you need the following things: 1. The

ANN: Django 1.4 release candidate 2 issued

Subject line says it all, and details, as always, are on the weblog: https://www.djangoproject.com/weblog/2012/mar/14/14rc2/ -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To

Re: Installing Django

On Tue, Mar 6, 2012 at 7:42 AM, Sophia wrote: > python setup.py install > > but it keeps giving me this error : > >   File "setup.py", line 70 >     if u'SVN' in version: >     ^ > SyntaxError: invalid syntax Most likely, you installed a 3.x version of Python.

ANNOUNCE: Django 1.4 release candidate available

We're nearly there! The Django 1.4 release candidate package is now available, and you can read all about it on the blog: https://www.djangoproject.com/weblog/2012/mar/05/14-rc-1/ -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." -- You received this message

Django 1.4 beta 1 released

Hot off the presses, it's the first Django 1.4 beta! Blog post with more information is here: https://www.djangoproject.com/weblog/2012/feb/15/14-beta-1/ -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." -- You received this message because you are subscribed to

  1   2   3   4   5   6   7   8   9   10   >