On Dec 12, 2007, at 3:19 PM, Robert Coup wrote:
>
> On 13/12/2007, Thomas Güttler <[EMAIL PROTECTED]> wrote:
>> How can you check that only authorized users can access
>> some files?
>>
>> Files which have a coresponding FileField in the model: How can
>> you test that only some people are allow
On Nov 30, 2007, at 8:54 PM, Simon Willison wrote:
>
> On Nov 30, 6:33 am, "Adrian Holovaty" <[EMAIL PROTECTED]> wrote:
>> I think we ought to call the release 2.0.
>
> I'm -0.5 on this (if that's possible). I understand the thinking
> behind it, but "1.0" isn't an arbitrary version number - it
On 8/26/07, James Bennett <[EMAIL PROTECTED]> wrote:
> I don't think it's really something that'll be voted on, at least not
> in a broad general sense. If releases happened based on people in the
> mailing list saying they want it to happen, we'd be on Django 3000 by
> now ;)
That's not exactly
On 8/23/07, Honza Král <[EMAIL PROTECTED]> wrote:
> Do you really need this? I am currently keeping my own two branches in
> git repository, that I synchronize with the master svn repository.
>
> It is very simple to do and completely painless. As you said yourself
> - since there are many convers
On 7/23/07, Eugene Lazutkin <[EMAIL PROTECTED]> wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Presently I maintain the Windows installer. Because of some reasons (the
> main one: core devs don't use Windows) it was not included in the
> official download page, so I "distribute" it
On 7/12/07, Peter Nixon <[EMAIL PROTECTED]> wrote:
>
> On Thu 12 Jul 2007, Jeremy Dunck wrote:
> > On 7/12/07, Peter Nixon <[EMAIL PROTECTED]> wrote:
> > > Am I just being dense, or is there no way in django's trac to monitor a
> > > bug for changes (and receive and email when it does) or even to
On 7/10/07, Sean Patrick Hogan <[EMAIL PROTECTED]> wrote:
> The "pythonic" way is a new addition to Django if I'm not mistaken.
>
> I personally prefer calling by string because (I'm assuming here) it doesn't
> load the function unless it needs to. So, if I have a URLConf that
> references 8 view
I feel your pain here. I never quite understood why the app, project,
whatever, had to care where it was being deployed. Or rather, why one
has to go out of his way to make URLs work in different contexts.
Coming from the Java world, this was something I had never run into,
and I was pretty put
On 7/7/07, Marty Alchin <[EMAIL PROTECTED]> wrote:
> So, like many other things these days, it comes down to a bikeshed.
> The Django authors built theirs the way they'd like it built, because
> it's what they needed for what they were doing. If you need your own,
> you're more than welcome to bu
On 8/22/06, James Bennett <[EMAIL PROTECTED]> wrote:
> 1. It's easier to "switch out" pooling utilities this way, or to
> switch between pooling and not pooling as circumstances dictate. When
> your framework tries to do connection pooling for you, it
> automatically gets harder and, depending on
On 8/7/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
> The thing is, there's no foolproof distinction between what settings
> should differ for dev environments and which ones are definitely for
> production environments. You gave the examples of MIDDLEWARE_CLASSES
> and ROOT_URLCONF, but those
On 8/7/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
>
> On 8/7/06, Kevin Menard <[EMAIL PROTECTED]> wrote:
> > I would be all for this. I never liked that the settings file
> > contains both project-wide and user settings. Since it's
> > project-
On 8/7/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
> We don't need a default solution for this. It's not within the scope
> of this project to tell people how they should organize their settings
> files. Take that opportunity to showcase your individualism.
With the lack of an endorsed conven
On 8/7/06, Michael Radziej <[EMAIL PROTECTED]> wrote:
> I strongly disbelieve that any fixed scheme of storing some
> settings separately will cover everybody's needs. It's easy
> enough to code your own thing in your settings.py.
You'll never cover everybody's needs, but you can cover the vast
On 8/7/06, Joe <[EMAIL PROTECTED]> wrote:
>
> Wouldn't you want to put your database settings (Username and password)
> in another file as well?
I would be all for this. I never liked that the settings file
contains both project-wide and user settings. Since it's
project-wide, it gets added to
On 7/27/06, Ian Holsman <[EMAIL PROTECTED]> wrote:
> perfect is what 1.0 is for.
I certainly hope this isn't the case. It'd kill me to see django get
caught up with the mythical 1.0 that seems to plague so many OSS
projects.
--
Kevin
--~--~-~--~~~---~--~~
You
On 7/27/06, Todd O'Bryan <[EMAIL PROTECTED]> wrote:
> Read about agile development. You can release stable code without
> freezing it.
I guess it depends on the definition of "stable." I agree that you
can have code that runs and runs well without freezing it. At some
point though, you gotta b
On 7/27/06, Jeremy Dunck <[EMAIL PROTECTED]> wrote:
> Two-phase email? "I'd like to svn up, report back when ready."
>
> Or, if too large a team, cron'd switchtower/capistrano task?
Heh, I'm not saying it's not doable. It is a pain in the neck though,
and is alleviated by a point release. I i
On 7/27/06, Joe <[EMAIL PROTECTED]> wrote:
> Hey, I'm with you 100%. I would use the development version if I
> could. Unfortunately, my project manager thinks 'development' means
> 'broken'. You know how those pesky project managers can be :)
I don't think it's an issue of "brokeness" so muc
Is there anyway to add a voting module to trac? A recent thread
discussed ways to improve the dev process, and I think something as
simple as a voting module could help quite a bit. The basic problem
I'm trying to address is the divide between what users and developers
feel are important. This
20 matches
Mail list logo
