So I hit another little snag today related to this. The
contrib.auth.middleware.LazyUser calls contrib.auth.get_user (knowing
where to get the user from based on the backend stored in
session['_auth_user_backend']), which will return an
authentication-backend-dependent user object. This user obj
One of the cool things about the admin app is the form building,
something that I wish were easier. Stuff like the AdminBoundField
would be nice to have outside of the admin (I don't know, is this
already easy to do?). I am assuming that the admin app will be
rewritten with the arrival of the ne
Ian Holsman wrote:
> luckily? for me I have a bit of time on my hands tomorrow and
> possibly monday.
> i could get a start on something 'forgish' which could then be used
> to critique/improve on.
Ian, does this mean you are working on a DjangoForge written in Django?
--~--~-~--~~-
I had some to make some changes to some models today that would result
in schema changes so I decided to give the schema-evolution branch a
go.
I didn't get far as the script I use to load sample data into my
applications failed [1] and trying to manually add data via my public
CRUD views failed
Hi,
I hit this bug 10 months ago when I first started using Django and it
still hasn't been addressed. As per my comments in the ticket I feel
that the use of the inet type in the postgresql backend is a special
case that is the root of the issue. Using a char(15) like every other
backend would f
On 8/30/06, Luke Plant <[EMAIL PROTECTED]> wrote:
Hi all,There has been no response on http://code.djangoproject.com/ticket/1400after mine and Simon's comments. I'd like to go ahead and revert that
one thing, but can the original committer (Russell) comment?I'm sure it seemed like a good idea at t
Done. Ticket #2619
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to [EM
This is great news!
One question comes to mind first, because I am nothing if not
self-absorbed. :) I wonder how much of the multi-db branch I have been
working on will be made irrelevant by this. Any thoughts on how the
sqlalchemy backend might support connecting different models to
different en
Robin Munn wrote:
>
> The notes on implementation that Adrian posted pretty much match what
> I'm thinking at this point. The plan is to make this 100% API
> compatible (if possible -- you never know what will turn up once you
> start implementing some idea), so that existing code doesn't need to
On Tuesday 29 August 2006 22:57, Ian Holsman wrote:
> FWIW.. there is a rouge bot going round in Australia
Since bots don't normally have colours, I'm guessing that must mean a
Communist bot. No doubt it's part of some international plan to
undermine capitalism, those pesky Communists at it
On 8/29/06, bradford <[EMAIL PROTECTED]> wrote:
>
> Hi, it seems like I'm constantly writing custom SQL code for everything
> because the django ORM cannot handle a lot of my requirements (which is
> perfectly understandable). Would it be such a bad idea to add an api
> to the django orm that's s
On 8/29/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
>
> Hi all,
>
> Spawned by the recent discussion of the big picture of Python Web
> frameworks, we've decided to start a new branch of Django development
> that uses SQLAlchemy (http://www.sqlalchemy.org/) as the underlying
> database library.
The source IP would be useful as well.
other things which *may* be useful might be the auth_user_id and
session_key of the request record.
FWIW.. there is a rouge bot going round in Australia which 'guesses'
URLs based on what it sees in javascript.
and i've also seen some spam bots guessing
hi,
(sorry to open this topic again, i understand that the core developers
have many other things to do etc...)
around 2 weeks ago we had this thread there about creating a branch for
the django-unicode conversion is it still the plan?
i'd just like to know what's the status... a "yes, we
Hi all,
Spawned by the recent discussion of the big picture of Python Web
frameworks, we've decided to start a new branch of Django development
that uses SQLAlchemy (http://www.sqlalchemy.org/) as the underlying
database library.
Robin Munn, author of an excellent SQLAlchemy tutorial
(http://www
On 8/29/06, Luke Plant <[EMAIL PROTECTED]> wrote:
> I'm currently getting tons of 'Broken INTERNAL link' e-mails from my
> live site, but they are incorrect -- sometimes the 'Referrer' URL
> doesn't even exist. I suspect it is some rather broken bot making all
> kinds of random requests, so I'd l
On 8/29/06, Luke Plant <[EMAIL PROTECTED]> wrote:
> There has been no response on http://code.djangoproject.com/ticket/1400
> after mine and Simon's comments. I'd like to go ahead and revert that
> one thing, but can the original committer (Russell) comment?
I'm +1 on reverting that change. The
I made a patch, in case anyone else also wants this.
http://code.djangoproject.com/ticket/2618
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-
I'm currently getting tons of 'Broken INTERNAL link' e-mails from my
live site, but they are incorrect -- sometimes the 'Referrer' URL
doesn't even exist. I suspect it is some rather broken bot making all
kinds of random requests, so I'd like to add 'User agent' to the
information that is sen
Hi all,
There has been no response on http://code.djangoproject.com/ticket/1400
after mine and Simon's comments. I'd like to go ahead and revert that
one thing, but can the original committer (Russell) comment?
Thanks,
Luke
--
Parenthetical remarks (however relevant) are unnecessary
Luke
On Tue, 2006-08-29 at 16:46 +, Andrew Durdin wrote:
[...]
> To quote from what I wrote in the ticket:
>
> > Finally, this patch should work without the decimal module: if the
> > decimal module is available, then models.DecimalField? attributes will
> > be decimal.Decimal instances; if not, t
Hey James,
On Sat, 2006-08-26 at 23:51 -0500, James Bennett wrote:
> Someone in IRC tonight was running into the problem described in
> ticket #343 tonight, and after a quick test I can verify it's still
> happening in trunk. I'm blacklisted in Trac right now (Tom's looking
> into it), so I'll po
On Mon, 2006-08-28 at 10:12 -0500, Tom Tobin wrote:
> On 8/28/06, Joel Heenan <[EMAIL PROTECTED]> wrote:
> >
> > I have noticed there is a great number of patches like mine that don't
> > ever seem to be reviewed and all seemed to be assigned to Adrian but
> > he seems to be concentrating on new f
On Tue, 2006-08-29 at 14:49 +0800, Slowness Chen wrote:
> simple_tag and inclusion_tag make writing simple template tags much more
> convenient.
> As the document says, "Another common type of template tag is the type that
> displays
> some data by rendering another template", e.g.
>
>
> {% f
On Mon, 2006-08-28 at 01:14 -0700, [EMAIL PROTECTED] wrote:
> Hi Russ,
>
> Nice work!
>
> FYI I submitted a patch (#2490 [1] ) a while ago to get runtests.py to
> produce an error if no DJANGO_SETTINGS_MODULE is in the env. Not sure
> if this is something you want, but I've updated it to work p
In a project I am working on, we need to store monetary values in the
database, and we want to avoid floats altogether so that we don't lose
precision or have representation errors. The existing FloatField was
not suitable for use, because it would sometimes return floats and
sometimes decimals, d
+1 to option 3.
Jacob
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to
On 8/29/06, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
> Personally, I find myself leaning towards option 3 - outside of testing, I
> can't see any use case for a template-rendering signal, and I don't like
> special cases. Instrumentation of the rendering system as part of the test
> framewor
Hi all,As a result of some performance concerns, Adrian has reverted the template rendering signals that were part of the recent test framework changesets. I was under the impression that the overhead of an dispatching a signal with no handlers would be negligible, so, to validate (or invalidate) A
Just in case someone is needing something like this too, i created a
patch: http://code.djangoproject.com/ticket/2615
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group,
30 matches
Mail list logo
