the Python 2.7 OS X installer builds a 'fat' Python install, which
*should work* with the OS X Apache2 install and mod_wsgi. The Python
2.6 OS X installer didn't support 64 bit architectures, necessitating
Apache2 to be trimmed 32 bit (
I'll certainly share my observations.
> I just did my first django deploy with nginx+fcgi with ssl and I have
> to say it was much easier to set it up and configure it than nginx
> +apache2+wsgi
> It also uses way less ram and CPU then the other deploy. Also I am
> using supervisord to manage
Thanks for all that. I'm going to:
1. go with a standard mod-wsgi setup in each Django site's VirtualHost
container and check performance,
2. then look at Gunicorn,
3. then assess whether running another server for static files is (for
my sites) worth it.
(while testing, I'm delivering static
I'm about to enter my first deployment learning curve, but after
reading James Bennett's post 'Let’s talk about WSGI' (http://www.b-
list.org/weblog/2009/aug/10/wsgi/) and further procrastinating by
reading through a whole pile of (horribly varying) tutorials and WSGI
guides, I'd like to know:
1.
Andrew Godwin from the South user group replied: "It looks like this
is a bug in the permissions-creating code, however, and not in South
itself (although it might be triggered by the way South fiddles with
the ORM)."
Ideas, anyone?
--
You received this message because you are subscribed to the
I should have also said: 'errr... help please, what now?'
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-us...@googlegroups.com.
To unsubscribe from this group, send email to
Thanks Anssi - that's very clear - Dave
> If you don't define null=True the database will enforce that all rows
> are not null. Of course when you add a field into the database, the
> row will have a null value by default for the old rows, and the
> database will give you an error.
>
> If null
I'm migrating James Bennett's 'Cotrane' blog app (adding a 'modified'
date field) using South on the existing app (with data already
present). These are the steps, and the traceback. Posting here because
the exact same error (in this post's title) also appears in Django and
Dmigrations bug reports
I have a Django blog app with data in the (SQLite) database and have
installed South so that I can add a 'modified' date field to the
'Entry' model. The field will initially be blank so I need blank=True
for Django's admin validation.
However, since it will also be empty in the database, do I
Ubuntu (quickest, easiest way to get started, ignoring various
options):
1. Check if you have Python's setup_tools (http://pypi.python.org/pypi/
setuptools) by typing (it will ask for your root password):
sudo easy_install Django
If that works, it may be all you need to get started. At this
To help guide answers, please state which platform are you using (OS
X, Windows, Linux)?
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-us...@googlegroups.com.
To unsubscribe from this group, send
Thanks for the advice. South installed, but glitches on converting
(that I'll no doubt iron out).
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-us...@googlegroups.com.
To unsubscribe from this
ah. forgot about the plain text in Google Groups... apologies. Again,
in English:
Given that Syncdb won't ever issue an alter table command ('no such
column'), that Schema Evolution is still in debate, that South is a
bit of an overhead if all you want to do is add a field to an existing
model -
Given that Syncdb won't ever issue an alter table command ('no such
column'), that http://code.djangoproject.com/wiki/
SchemaEvolution">Schema Evolution is still in debate, that http://south.aeracode.org/;>South is a bit of an overhead if
all you want to do is add a field to an existing model -
Update: removed 64-bit MySQL, installed 32-bit version from package,
re-installed MySQL-python after removing with easy_install -m (which
now also removes the line in easy-install.pth). >>>import MySQLbd is
okay. Got warning so will see if okay.
--
You received this message because you are
I've been happily using (32-bit) Django and MySQL in development on an
existing machine running OS X 10.4 Tiger, and have set up a similar
environment in 10.5 Leopard on a new 64-bit MacBook, with a
(separately) working MySQL and Python 2.6.4.
Now I want them to communicate, easy_install
I've just removed my old Django 1.0 dir to install 1.1 (as per the
instructions on the Django site):
http://docs.djangoproject.com/en/dev/topics/install/#removing-old-versions-of-django
But this leaves django-admin.py under (on Mac OS 10.4.11):
First, thanks for the responses. Second, to answer the questions:
1.
> - how would you like to handle (or not-handle) overlapping
> ranges? ("100 ..150, 120, 145-155")
as above, in order, lowest number in range first
2.
> - are ranges always specified the same way? (".." vs. "-")
According
I have some data (page number references) that looks like this:
320, 387..90, 410, 500
or (sustituting numerical .. ranges for conventional dashes)
320, 387-90, 410, 500, 634
I'd just like to know the most Django-esque way of creating a model
for these?
The requirements are:
1. they're all
> We're always open to documentation improvements; thanks for offering to help.
The latest version (under revision before becoming HTML) of my
'absurdly simple' try-Django-locally for OS X is here:
ecoconsulting.co.uk/python/django-install.txt
> If you're installing from a downloaded version of
After reading about other OS X user's Django install problems, I'm
attempting to write up the simplest, clearest possible, completely
unambiguous, instructions for other OS X users here:
http:ecoconsulting.co.uk/python/django-install.txt
but obviously I need to get it right first, and...
...I've
21 matches
Mail list logo
