James Bennett wrote:
> On 8/9/06, Linicks <[EMAIL PROTECTED]> wrote:
>> 1. Chris, would it be reasonable to move your work to Dojo?
>
> From the looks of things, that's how he'd implemented it at first; he
> then switched to YUI.
Do you know the reason? I am curious to know what was wrong.
T
On 10/08/06, Scott Paul Robertson <[EMAIL PROTECTED]> wrote:
> On Wed, Aug 09, 2006 at 08:00:31PM -0700, Gary Wilson wrote:
> > > Scathing comments are encouraged.
> >
> > line 68 of patch:
> > if not username and password is not Null: # we need a user/pass
> > Should be None
On Wed, 2006-08-09 at 23:50 -0500, James Bennett wrote:
> [...]
> And as much as some people I've talked to have been wailing and
> gnashing teeth about Rails being into Mac OS X 10.5 while Django
> isn't, well, I don't envy somebody who gets shipped as part of a major
> operating system when it c
On 8/9/06, Jason Huggins <[EMAIL PROTECTED]> wrote:
> I can see how a policy like that is "tricky"... What's to keep an evil
> blackhat from subscribing to the very same list so he he knows when to
> get busy cracking sites using the same information?
I've been watching people go round and round
James Bennett wrote:
> > 3) Is there any sort of policy or promise on how many versions back
> > Django devs are willing to go back and support?
>
> The documentation page Malcolm linked states that patches will be
> developed for the current release and the two releases previous to it.
> That see
Scott Paul Robertson wrote:
> > Also, in the ldap setup I deal with, you must bind to the server using
> > a service account before attempting a bind with the user-supplied
> > credentials. The process goes something like
> >
> > 1. Retrieve the username and password from the user.
> > 2. Bind to
Jeremy Dunck wrote:
> True, but Rails had lots of buzz and has -lots- of prod systems. Of
> the 2 people I talked to with prod rails systems, neither had heard of
> this 3 hours after the posting. I only knew because of luck on
> prog.reddit.
Same here, programming.reddit.com is my most hit sit
On 8/9/06, Jason Huggins <[EMAIL PROTECTED]> wrote:
> 2) How should the affected users be notified? Having read the above
> doc, I think this could use some more detail.
One would hope that anyone who's using Django is subscribed to
django-users and/or watches the Django blog (or that a company w
Malcolm Tredinnick wrote:
> See
> http://www.djangoproject.com/documentation/contributing/#reporting-security-issues
Sorry I didn't read that first before posting here. Though I did a Trac
search for "security" and that page didn't come up in the first few
search results...
Though, looking at th
On Wed, Aug 09, 2006 at 08:00:31PM -0700, Gary Wilson wrote:
> > Scathing comments are encouraged.
>
> line 68 of patch:
> if not username and password is not Null: # we need a user/pass
> Should be None
d'oh! Figures I'd mistype something like that.
> And how about mov
On 8/9/06, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> I'm not completely sure I agree with the way the Ruby team are handling
> this release, but since I don't know the details yet, I can't really
> work out what is happening; they may have very good justification for
> the way they are doing
Malcolm Tredinnick wrote:
> On Wed, 2006-08-09 at 19:25 -0700, Linicks wrote:
> [...]
> > AJAX integration is a nice touch, but I think that the use of YUI goes
> > against the established use of Dojo with Django.
>
> Where are we using Dojo at the moment?
>
> Malcolm
Malcolm,
I'm not sure how
On 10/08/2006, at 12:45 AM, Adrian Holovaty wrote:On 8/9/06, Chris Long <[EMAIL PROTECTED]> wrote: Hopefully that answers some of your concerns. I'm curious as to thecommunities take on it, if in general the opinion is to remove it thenI will. I personally think the admin interface would work well
On 8/9/06, Bryan Chow <[EMAIL PROTECTED]> wrote:
> Ian Clelland and I have been working on a way to address the problem
> that Django FileFields and ImageFields can't be cleared once they've
> been set. We've posted a proposed solution here [1].
This is certainly a long-standing wart in Django, a
On 8/9/06, Chris Long <[EMAIL PROTECTED]> wrote:
> Hopefully that answers some of your concerns. I'm curious as to the
> communities take on it, if in general the opinion is to remove it then
> I will. I personally think the admin interface would work well with
> some AJAX built into it, but I kno
On 8/9/06, Linicks <[EMAIL PROTECTED]> wrote:
> 1. Chris, would it be reasonable to move your work to Dojo?
>From the looks of things, that's how he'd implemented it at first; he
then switched to YUI.
--
"May the forces of evil become confused on the way to your house."
-- George Carlin
-
Scott Paul Robertson wrote:
> On Tue, Aug 01, 2006 at 12:08:25PM -0700, Scott Paul Robertson wrote:
> > I'm actually doing LDAP auth with something I wrote myself, which I feel
> > is a little more general than the mentioned code (not that I'm
> > opinionated or anything). I'll be posting it in a
Linicks wrote:
>
> AJAX integration is a nice touch, but I think that the use of YUI goes
> against the established use of Dojo with Django. After reading the
> proceeding threads in this post, a couple of questions come to mind:
>
> 1. Chris, would it be reasonable to move your work to Dojo
Hi All,
Ian Clelland and I have been working on a way to address the problem
that Django FileFields and ImageFields can't be cleared once they've
been set. We've posted a proposed solution here [1].
Our solution differs from the one proposed in Ticket #22 [2] in that
it's somewhat simpler, isn't
On Wed, 2006-08-09 at 19:25 -0700, Linicks wrote:
[...]
> AJAX integration is a nice touch, but I think that the use of YUI goes
> against the established use of Dojo with Django.
Where are we using Dojo at the moment?
Malcolm
--~--~-~--~~~---~--~~
You receive
> Hopefully that answers some of your concerns. I'm curious as to the
> communities take on it, if in general the opinion is to remove it then
> I will. I personally think the admin interface would work well with
> some AJAX built into it, but I know that isn't the case with everyone.
> Comments?
On Wed, 2006-08-09 at 18:41 -0700, Jason Huggins wrote:
[...]
> A few questions:
> 1) If there was critical security flaw found in Django (any version)
> today, are there plans in place on how to deal with it? If so, are
> those plans posted anywhere? If not, let's roll up our sleaves and do
> it!
I'm on the Apache security list, and I'll offer my 2c's on how they do it.1) A security@ email alias which is private and is a alias for the core developers. be prepared for a *LOT* of spam, and a lot of questionswhich should have been asked on dev@ or [EMAIL PROTECTED] security providers like to s
I'm really feeling for our Rails Core friends... they're getting
blasted right now for not having a complete policy for releasing and
communicating urgent security flaws. I'm not poking fun, this is pretty
serious stuff.
Read here for some of the comments they're getting today via
Reddit.com:
"Ma
On Wed, 2006-08-09 at 21:51 +0200, gabor wrote:
[...]
> phew... the immortal
> how-tolerant-we-should-be-when-doing-unicode-conversion problems :-)
Agreed. This is much easier on my side of the fence (lobbing problems),
than your side (solving them).
> i generally prefer to do as little guesswo
On Tue, Aug 01, 2006 at 12:08:25PM -0700, Scott Paul Robertson wrote:
> I'm actually doing LDAP auth with something I wrote myself, which I feel
> is a little more general than the mentioned code (not that I'm
> opinionated or anything). I'll be posting it in a day or so once it's
> cleaned up a bi
Malcolm Tredinnick wrote:
> A couple of comments on the patch itself. I realise it's only a proof of
> concept at the moment, so take as more things to think about when you
> want to tidy it up:
>
> (1) A docstring like """needed to workaround the cgi.parse_sql
> unicode-problem""" is not very fu
Ivan Sagalaev wrote:
> First of all, Gabor, thank you very much for doing this!
>
thanks :)
> gabor wrote:
>> today i experimented a little with the django source code,
>> and here are the results.
>>
>> if you apply a very small patch (65lines, attached), you can write a view
>> completely in
On 8/9/06, Tom Tobin <[EMAIL PROTECTED]> wrote:
>
> I've already gotten the first case working, and I'll tackle the second
> after work tomorrow; I'll report back with my thoughts after comparing
> the two.
I actually implemented the second case (a ``takes_manipulator``
decoration) last night as
First of all, Gabor, thank you very much for doing this!
gabor wrote:
> today i experimented a little with the django source code,
> and here are the results.
>
> if you apply a very small patch (65lines, attached), you can write a view
> completely in unicode.
> means:
> - GET/POST contains uni
On 8/9/06, Chris Long <[EMAIL PROTECTED]> wrote:
> Hopefully that answers some of your concerns. I'm curious as to the
> communities take on it, if in general the opinion is to remove it then
> I will. I personally think the admin interface would work well with
> some AJAX built into it, but I kno
Hi all,
Thanks for your responses - concerns have been relieved.
I wasn't aware that there was no obligation to include the SoC stuff.
I think that the admin would gain a lot from having more JS/AJAX stuff
and that it would be a wise decision to pick a framework and run with
it. However as soon
On Wed, 2006-08-09 at 04:04 -0700, David Martin wrote:
[...]
> ImportError: No module named __future__
>
>
> I've setup Django before without major problems, but I'm setting it up
> on another personal server, and for some reason this time I get this
> error message. when the httpd.conf -> Pyth
from my understanding having YUI in this section is very localized, and would not affectyour choice of AJAX library to use within your applications.On 09/08/2006, at 9:05 PM, Chris Long wrote:Hi,I'm the developer working on the branch.A few things, hopefully to answer your concerns.1) The HTML and
just as a follow up to this, after debugging it with Malcom,we discovered we weren't copy()'ing the extra context parameter when we passed it into the request.so the previous request was modifying it and we then passed it back into the new one.On 07/08/2006, at 9:57 AM, Ian Holsman wrote:On 07/08/2
Hi,
I'm the developer working on the branch.
A few things, hopefully to answer your concerns.
1) The HTML and JS is written that the AJAX can be turned off very
easily(currently it works better with JS disabled then enabled). And I
plan on implementing a method of selecting if you wish to use t
Mod_python error: "PythonHandler django.core.handlers.modpython"
Traceback (most recent call last):
File "/usr/lib/python2.4/site-packages/mod_python/apache.py", line
287, in HandlerDispatch
log=debug)
File "/usr/lib/python2.4/site-packages/mod_python/apache.py", line
457, in import_mod
Shouldn't the UTF-8 encoding be also defined in all files as described
here: http://www.python.org/dev/peps/pep-0263/ ?
That is using
#!/usr/bin/python
# -*- coding: UTF-8 -*-
at the beginning of python code files.
This works pretty good at least when you need to create new instances
of models
Hey John,
On Wed, 2006-08-09 at 10:41 +0100, John Sutherland wrote:
> Hi all,
>
> I don't want sound like an arse, but has anyone seen changeset 3541 [1]?
>
> I understand it's still a branch [2], but are we going to be getting
> all that YahooUI stuff in trunk?
>
> I don't want to get in a fl
Hi all,
I don't want sound like an arse, but has anyone seen changeset 3541 [1]?
I understand it's still a branch [2], but are we going to be getting
all that YahooUI stuff in trunk?
I don't want to get in a flame-war about the whole AJAX/JavaScript
thing, but I'm of the impression that Django
40 matches
Mail list logo
