2010/2/28 Ulrich Petri :
> ~/ python2.6
> Python 2.6.4 (r264:75821M, Oct 27 2009, 19:48:32)
> [GCC 4.0.1 (Apple Inc. build 5493)] on darwin
> Type "help", "copyright", "credits" or "license" for more information.
from urllib2 import urlopen
urlopen('http://пример.испытание/')
> >
Yeah, i
On Feb 27, 3:06 am, Russell Keith-Magee
wrote:
> I'm a little confused by this ticket.
>
> The original report was about something that is clearly a bug -- the
> inconsistency between block handling for {% if %} and {% ifequal %}.
> I'm 100% in agreement that this inconsistency should be fixed.
>
Hi Jacob,
Thanks for your answer.
I already gave intermediate models a look but I'm not feeling like defining a
dozen useless model - no added value - and loosing a couple of API calls are
worth just because my fields are labeled "id_fieldname" instead of "fieldname".
Sorry for the annoyance.
X
Hi Xavier --
This is a question better asked on django-users -- django-developers
is for discussion of the development of Django itself, not usage
questions.
As a brief answer to your question, you'll want to take a look at
defining a custom intermediary model:
http://docs.djangoproject.com/en/de
Hi,
I gave Django 1.2 a go but I had some issues with legacy database support.
I have several ManyToMany relations with an intermediate model that doesn't
have an id field (only 2 fields pointing on each table).
With Django 1.1, I abused this snippet :
http://www.djangosnippets.org/snippets/962
On Sun, Feb 28, 2010 at 11:40 PM, Jacob Burch wrote:
> Thanks all for the helpful discussion here. From the sounds of thing,
> my course of action will be:
>
> 1) Get a patch that throws a FutureDeprecationWarning when cmemcache
> is used + Change of the docs to note the coming deprecation of
> cm
On Mon, Mar 1, 2010 at 9:47 AM, Luca Sbardella wrote:
> Hi there,
>
> I just switch from 1.2 beta 1 to svn version and the
> ModelAdmin.response_action is not working as before
Yes, this has been reported at least twice in the tracker (see
http://code.djangoproject.com/ticket/12962) and at least
Hi there,
I just switch from 1.2 beta 1 to svn version and the
ModelAdmin.response_action is not working as before.
For example it does not delete objects when confirming a bulk
deletion.
The problem seems to be in the beginning of the function
if 'index' not in request.POST:
return None
By
> I've never understood the desire for more magical behavior here. My
> apps have a settings.py that imports django.conf.settings and provides
> any necessary defaults for unset settings; the rest of my app imports
> from there. Works great, easy to look and see what settings my app
> consumes and
On Mon, Mar 1, 2010 at 6:59 AM, George Karpenkov wrote:
> Thanks for the reply.
>
> If it wouldn't take too much time, can you please point me to those
> discussions?
>
>
This ticket is one I recall:
http://code.djangoproject.com/ticket/10768
Karen
--
You received this message because you are
Thanks for the reply.
If it wouldn't take too much time, can you please point me to those
discussions?
All I was able to find was that thread
http://groups.google.com/group/django-developers/browse_thread/thread/1edf77c9c8b1101d/06d4775747a5a127?lnk=gst&q=admin+action+selected#06d4775747a5a127
w
11 matches
Mail list logo