;malformed" in URI's path part?
So, it seems not obvious to handle it. Let's refuse the temptation to
guess. ;-)
Regards,
--
Luciano Pacheco
blog.lucmult.com.br
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To po
Hi all,
Have you guys seen this?
http://www.ocert.org/advisories/ocert-2011-003.html
PDF with some more explanation:
http://www.nruns.com/_downloads/advisory28122011.pdf
Regards,
--
Luciano Pacheco
blog.lucmult.com.br
--
You received this message because you are subscribed to the Google
d to djang-dev
list, but I haven't found it.
https://www.djangoproject.com/community/
Thanks,
--
Luciano Pacheco
blog.lucmult.com.br
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to djang
g :-) ?
We change the database schema and provide the SQL scripts to migrate the 4
supported backends (sqlite, mysql, postgres and oracle). This script are
needed "only" for upgrade projects, new projects it's just a normal path.
Is that hard, inconvenient or bad?
In
alidation environment to analyse the changes before
production.
This current limitation doesn't bother me, but all this concerned about
database schema change does. :-)
Regards,
--
Luciano Pacheco
blog.lucmult.com.br
--
You received this message because you are subscribed to the Google G
version and path:
>>> import django
>>> django.VERSION
(1, 3, 0, 'final', 0)
>>> django.__file__
'/home/lucianopacheco/src/tmp_py/local/lib/python2.7/site-packages/django/__init__.pyc'
So, it will be much more clear to people not f
t."
> sys.exit(1)
>
This "import django" will work even when django is not installed, because
usually "python setup.py " is ran from checkout of django, that contains
the valid folder (python package) named "django". So, this "import django"
will impor
s emerge. We have been waiting this
common sense to emerge without any builtin support, maybe with the basic
api would have more people involved with.
[].
Luciano Pacheco
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post
sions', 'devserver')
MIDDLEWARE_CLASSES += ('debug_toolbar.middleware.DebugToolbarMiddleware',)
On the main topic, I'm in favor of PROJECT_ROOT settings, it's a common
practice, and isn't that bad, once in production it can be a mount point or
overwritten on local_
s changes in the docs and memcache backends, but there isn't any test,
because I couldn't figure out how to test them. :( Any advice on how to
test them?
Any feedback is welcome, I'm willing to make any necessary changes to get
it on the 1.6 train :)
[],
--
Luciano Pacheco
blog.lucmu
x27;s reasonable to assume that by default we want our data to
be consistent.
Regards,
Luciano Pacheco
On 17/10/2013 10:47 AM, "Cal Leeming [Simplicity Media Ltd]" <
cal.leem...@simplicitymedialtd.co.uk> wrote:
> Thank you for the detailed reply, much appreciated.
>
> I think
11 matches
Mail list logo