On 8/6/06, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> You sound like you are wanting the full configurability of
> django-admin.py, which is quite different. In that case, do what
> django-admin.py does: call management.execute_from_command_line(...) but
> pass in your own action_mapping dict
On Sun, 2006-08-06 at 11:02 +0800, limodou wrote:
[...]
> I'v tried the new setup_environ function, and the code is:
>
> import settings
> from django.core.management import setup_environ
> setup_environ(settings)
>
> You can not leave the parameters of setup_environ blank.
Oh, true. This is de
The other benefit of what limodou proposes is that is makes it really easy to generate anothersecret key when it is required.for example I've got 4-5 sites using basically the same settings file. when I want to create anotherI usually just copy the settings file, and alter the cookie name and secre
On Sat, 2006-08-05 at 22:58 -0400, Todd O'Bryan wrote:
> Am I looking in vain for file tests in the test suite? My guess is
> that I am, which makes sense, because I'm not sure how exactly one
> would go about providing tests for file uploads.
You are indeed looking in vain. In fact, at the m
On 8/6/06, Todd O'Bryan <[EMAIL PROTECTED]> wrote:
>
> Am I looking in vain for file tests in the test suite? My guess is
> that I am, which makes sense, because I'm not sure how exactly one
> would go about providing tests for file uploads.
>
> Any suggestions?
>
> Todd
>
Maybe you can test exist
On 8/6/06, Todd O'Bryan <[EMAIL PROTECTED]> wrote:
>
> On Aug 5, 2006, at 10:32 PM, Malcolm Tredinnick wrote:
>
> > On Sun, 2006-08-06 at 07:05 +0800, limodou wrote:
> >> If I write my own scripts which will use models and deal with them,
> >> but I also need to set PYTHONPATH and DJANGO_SETTING_M
Am I looking in vain for file tests in the test suite? My guess is
that I am, which makes sense, because I'm not sure how exactly one
would go about providing tests for file uploads.
Any suggestions?
Todd
--~--~-~--~~~---~--~~
You received this message becaus
On Sat, 2006-08-05 at 22:07 -0400, Todd O'Bryan wrote:
> On Aug 5, 2006, at 8:12 PM, Malcolm Tredinnick wrote:
>
> >> Yes, this will be slower than having Apache serve the file directly,
> >> but it has the huge advantage that the file is served as the result
> >> of a view. That means you can do
On Aug 5, 2006, at 10:32 PM, Malcolm Tredinnick wrote:
> On Sun, 2006-08-06 at 07:05 +0800, limodou wrote:
>> If I write my own scripts which will use models and deal with them,
>> but I also need to set PYTHONPATH and DJANGO_SETTING_MODULE evn
>> variables. I know manage.py can do this thing, an
On 8/6/06, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
>
> On Sun, 2006-08-06 at 07:05 +0800, limodou wrote:
> > If I write my own scripts which will use models and deal with them,
> > but I also need to set PYTHONPATH and DJANGO_SETTING_MODULE evn
> > variables. I know manage.py can do this thi
On Sun, 2006-08-06 at 07:05 +0800, limodou wrote:
> If I write my own scripts which will use models and deal with them,
> but I also need to set PYTHONPATH and DJANGO_SETTING_MODULE evn
> variables. I know manage.py can do this thing, and I think why cann't
> I use it to run my scripts which need
On 8/5/06, limodou <[EMAIL PROTECTED]> wrote:
> When you create a new project, django-admin.py will create a
> SECRET_KEY and saves it in settings.py. Sometimes we are developing an
> open source project, so we'll bring settings.py to public also. And
> also make SECRET_KEY openned. So I think if
On Aug 5, 2006, at 8:12 PM, Malcolm Tredinnick wrote:
>> Yes, this will be slower than having Apache serve the file directly,
>> but it has the huge advantage that the file is served as the result
>> of a view. That means you can do all kinds of interesting permission
>> checking, url mapping, an
On Sun, 2006-08-06 at 09:41 +0800, limodou wrote:
> When you create a new project, django-admin.py will create a
> SECRET_KEY and saves it in settings.py. Sometimes we are developing an
> open source project, so we'll bring settings.py to public also. And
> also make SECRET_KEY openned. So I thin
When you create a new project, django-admin.py will create a
SECRET_KEY and saves it in settings.py. Sometimes we are developing an
open source project, so we'll bring settings.py to public also. And
also make SECRET_KEY openned. So I think if django-admin.py could
create a file(maybe .key or key
On Aug 5, 2006, at 5:25 PM, Ivan Sagalaev wrote:
>
> Todd O'Bryan wrote:
>> Would it be better to expose the file-like object that comes with a
>> file upload, rather than reading the file's whole content into memory
>> (or into the server's file system, if the patch gets checked in)?
>> It's eas
On Sat, 2006-08-05 at 15:54 -0400, Todd O'Bryan wrote:
> It seems that requests for some way to store binary data in the
> database is a perennial request. I've seen comments (I think Adrian
> said it "opens a can of mutated worms."), but never a real
> discussion of what the problems would
If I write my own scripts which will use models and deal with them,
but I also need to set PYTHONPATH and DJANGO_SETTING_MODULE evn
variables. I know manage.py can do this thing, and I think why cann't
I use it to run my scripts which need these env variables setting. So
If I can run my scripts ju
Chris,
Thanks for keeping us in the loop! Row Level Permissions and Generic
Authorization are probably the most important new features in Django
for me at the moment so its nice to know that things are going well.
I'm really looking forward to using it on my current project. Many
thanks to all
Todd O'Bryan wrote:
> Would it be better to expose the file-like object that comes with a
> file upload, rather than reading the file's whole content into memory
> (or into the server's file system, if the patch gets checked in)?
> It's easy to retain backward compatibility by just having a
Agreed, it is a blunt solution. However, you could use it to address
the requirement of allowing different groups of users different upload
limits by using a separate virtual server for each group of user, e.g.
https://admin.yoursite.com for content providers and
http://www.yoursite.com for public
OK. That answers one concern. But that's a very blunt tool. You can't
for example, allow some users (say content providers) to upload
multiple megabytes, but limit others (content consumers, perhaps) to
much smaller sizes.
Todd
On Aug 5, 2006, at 3:57 PM, Bryan Chow wrote:
>
> You can use
You can use Apache's LimitRequestBody directive to restrict the size
of accepted uploads.
http://groups.google.com/group/django-users/browse_thread/thread/ca95963aaa33ce1e
On 8/5/06, Todd O'Bryan <[EMAIL PROTECTED]> wrote:
> The way Django ships, isn't it possible for a user to hijack the
> se
It seems that requests for some way to store binary data in the
database is a perennial request. I've seen comments (I think Adrian
said it "opens a can of mutated worms."), but never a real
discussion of what the problems would be.
There's a recent ticket, #2417, that adds support for "sm
The way Django ships, isn't it possible for a user to hijack the
server by uploading HUUUGE files? Because the files are stored in
memory, this seems like it could be a very bad thing.
There's a ticket, #2070, with a patch that buffers files in small
chunks, so that no more than about 64k i
Yep, for the moment, we will definitely use the full django source,
generate the settings and gradually try to exclude unnecessary sections
of the framework where we can. After a gentle glance, it looks like
http, middleware, shortcuts, template, templatetags, views can be cut
out straight away. f
Hello,
If you just want to use the model API, there is no problem .
Just follow the example at
http://www.djangoproject.com/documentation/tutorial1/#playing-with-the-api
You just have to setup (in __init__.py by example) DJANGO_SETTINGS_MODULE env
variable. Then you'll be able to import your m
It think the challenge might be if you want to use the views and manipulators component of django.you might be able to write your financial app so that you can have a QT and web front end with the same code.cheersIan.On 05/08/2006, at 7:12 PM, Malcolm Tredinnick wrote:On Sat, 2006-08-05 at 01:18 -0
On Sat, 2006-08-05 at 01:18 -0700, chillisource wrote:
> Hi,
>
> We are students developing an open source financial application using
> Python & Qt4. We really like Django's database API and would like to
> separate it from the web/middle ware. However, we fear that it might
> not be modular eno
Hi,
We are students developing an open source financial application using
Python & Qt4. We really like Django's database API and would like to
separate it from the web/middle ware. However, we fear that it might
not be modular enough to just 'take out'.
Has anyone had any experience or successfu
30 matches
Mail list logo
