One thing you can do is turn on the option 'Link with editor' on your
package\project explorer view. You have the *down arrow* ['View Menu'
tooltip] and an option at the bottom--'Link with Editor'.
That way, any active file in the editor will highlight the file in
your view, and you can keep trac
Hello everyone. I've only recently started developing app with Django
and in Python as well. I have a fair experience in developing web apps
on frameworks in PHP and I'm really trying to make a commitment on
doing my first Django app properly (all the good methodologies and
practices included)
Th
Django more as a library, the applications as simply packages
and focusing on the Python imports for linking it all up made
everything perfectly clear in the end.
Thanks for hitting me with it Malcom!
On Apr 7, 2:56 pm, Malcolm Tredinnick
wrote:
> On Tue, 2009-04-07 at 04:36 -0700, kRON wrote:
>
I haven't used that many pluggable Django apps, but I'd say it really
depends as you go from application to application. The first step is
to decide where your pluggables will live. I like to keep pluggables
that are used by my project specific apps under %project%.apps.contrib
for clarity's sake.
Basically, you can't use Django models on Google App Engine. So, in
brief, all Django applications that interact with a datastore will not
work on Google App Engine.
But - don't despair. There are two Django distributions ported for
Google App Engine that I'm aware of:
- http://code.google.com/p
I've set up my Media class for a widget as such:
class InternationalSlugWidget(forms.TextInput):
class Media:
js = ('js/international_slug.js')
The problem is Django keeps pumping out the following import
statements:
...etc
My media root string looks
--~--~-~--~~-
Sorry for the repost, somehow I've submitted the form.
I just wanted to add that my media url looks as MEDIA_URL = '/media/'
Can anyone steer me the right way for fixing this?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Problem solved, my fault - just noticed it was expecting to traverse a
tuple;
js = ('js/international_slug.js',) fixed the problem
On May 7, 10:16 am, kRON wrote:
> Sorry for the repost, somehow I've submitted the form.
>
> I just wanted to add that my media url look
Thanks for posting the links, I'll be sure to try and test it during
the weekend.
On Jun 5, 1:37 pm, Michelschr wrote:
> Hello everyone,
>
> What are the current trends about the best test coverage tools to use
> with Django?
> Do you have feedback or recommendations for me?
>
> Up to now, I fou
I really like Mike's post and I think it all boils down to what he's
said. There's not much to add except other personal preferences and
delicacies you take onto a new project.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
I have a web application developed as a Django site that I'd like to
distribute along to my clients on Windows; their production
environment won't have Apache and MySQL preinstalled. To avoid having
to manually deploy Apache and MySQL and look silly if I run into any
hiccups whilst configuring the
I've recently read about `clean_fields()` and decided to move some
stuff to I that I was doing in my `pre_save` handler previously. My
tests failed and then I noticed that neither `clean_fields()` nor
`full_clean()` was ever called before saving the model.
The documentation says that only `clean()
Nope, no caveat there. You'r perfectly free to design your own URLs as
you like.
Ultimately, means you can also have a conflicting situation where you
decide you don't want to have a trailing `/` but you include URLs from
a 3p django application that do.
On Jan 28, 1:54 am, Brett Thomas wrote:
>
I wager that Javier already has the best possible answer, but,
nonetheless, I'll try to elaborate it a just a bit more.
When a client requests a resource from your Web server that's handled
by PHP, what happens is that an instance of PHP is fired that
initializes the request data in the globals (l
What your looking for is exactly achieved by providing a custom
default file storage class.
Have a look at:
http://docs.djangoproject.com/en/1.2/ref/settings/#default-file-storage
http://docs.djangoproject.com/en/1.2/topics/files/#file-storage
Here's a simple example of how it might work in your
15 matches
Mail list logo
