Hi Idan,
Those are two great topics, congratulations to you and to us :) and
good luck!
Wim
--
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
Great work!
As the final release has not yet been announced, did something go
wrong?
Could you please post a small status update?
Thanks,
Wim
On Mar 4, 7:00 am, James Bennett wrote:
> Tonight we're proud to announce the first release candidate for Django
> 1.3; if all goes well, the final rel
On Tue, Mar 22, 2011 at 6:23 PM, Wim Feijen wrote:
> Great work!
>
> As the final release has not yet been announced, did something go
> wrong?
>
> Could you please post a small status update?
My apologies -- we haven't been very effective in communicating the delays here.
We've had a couple of
I personally would greatly appreciate update in docs to show "best
way" to handle per enviroment settings / sensitive settings, as now
there is many ways :)
Consider when one has his local development enviroment with locmem
cache and sqlite3 db, and staging server with MySQL / memcache and
produc
On 22/03/11 12:44, Kristaps Kūlis wrote:
> I personally would greatly appreciate update in docs to show "best
> way" to handle per enviroment settings / sensitive settings, as now
> there is many ways :)
> Consider when one has his local development enviroment with locmem
> cache and sqlite3 db,
Hi Idan,
Good luck! I'll expecting some exciting news! :D
2011/3/22 Wim Feijen
> Hi Idan,
>
> Those are two great topics, congratulations to you and to us :) and
> good luck!
>
> Wim
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers" group.
On Thu, Mar 17, 2011 at 7:44 PM, Marco Louro wrote:
> I don't really know how to approach this issue the best way, so I'm
> just going to be direct, I'd love to see Django provide support for
> django.core.urlresolvers.reverse (at least) on the client (in
> JavaScript).
>
> [...]
>
> So my questio
This is my django snippet to calculate custome stmts but it displays
the error
from optionsAlpha.models import MarketUpdate
from datetime import datetime
from django.db.models import Q
def stock_up(ticker, test_start_date):
#stock_value=0
mu1 = MarketUpdate.objects.filter(Q(stock_symbol=ticker) &
Hi there,
I have not used this myself, but believe that "Q objects" don't
support & operator as you use it. So it's really a Python error, not
Django error.
FYI, you need Q objects only to provide "OR" functionality. For "AND"
functionality, you only need:
mu1 = MarketUpdate.objects.filter(stoc
2 more comments ( I just noticed ):
- these questions should be sent to django-users, not django-developers
- why go through all stock values to find the best one in the loop
(you could use agregates for that) and then only return count?
Cheers
Jirka
--
You received this message becau
These are some auth settings and models I propose to account for the
generally
raised questions for auth.User flexibility.
Settings:
- AUTH_USER_EMAIL_UNIQUE
If the email should be unique for users. It is a rare case when a website
would have users sharing emails. It is more likely oth
On 17/03/11 07:47, Vivek Narayanan wrote:
> Hi,
>
> This is my proposal for the customizable serialization idea:
Hi Vivek - sorry about the long reply-wait on this! My initial thoughts
are below.
> The user can define methods beginning with “meta_” to add metadata
> about each field. And function
It's worth pointing out that manage.py runserver isn't likely to ever
support serving those files even if the header arrives in core. It's
explicitly not appropriate for any kind of production use, fallback or
otherwise. If you really need support for your development work (and
checking the headers
I would be in support of a manage.py command to change the secret key,
just as a convenience. I'd be happy to implement it.
Matthew Roy said:
> If I understand
> how it works the compromise of the SECRET_KEY alone doesn't put you in
> serious hot water unless the attacker can also intercept traffi
On Tue, Mar 22, 2011 at 6:44 AM, Kristaps Kūlis
wrote:
> I personally would greatly appreciate update in docs to show "best
> way" to handle per enviroment settings / sensitive settings, as now
> there is many ways :)
> Consider when one has his local development enviroment with locmem
> cache a
Why not just do an import for your custom settings?
try:
from site_settings import *
except ImportError:
pass
On Mar 22, 2011, at 5:51 PM, Ian Kelly wrote:
> On Tue, Mar 22, 2011 at 6:44 AM, Kristaps Kūlis
> wrote:
>> I personally would greatly appreciate update in docs to sho
On Tue, Mar 22, 2011 at 4:49 PM, Matt Robenolt
wrote:
> Why not just do an import for your custom settings?
>
> try:
> from site_settings import *
> except ImportError:
> pass
No particularly compelling reason that I know of, the import machinery
is just unnecessary in this case. T
That's just interesting. I've never seen the use of `execfile()` before. We use
a devsettings.py and use it to override an individual server or local settings,
and then on the live/deployed server, no devsettings.py is even included. Hence
the try...except wrapped around it. It's a nice little p
On 03/22/2011 07:05 PM, Ian Kelly wrote:
> On Tue, Mar 22, 2011 at 4:49 PM, Matt Robenolt
> wrote:
>> Why not just do an import for your custom settings?
>>
>> try:
>>from site_settings import *
>> except ImportError:
>>pass
>
> No particularly compelling reason that I know of,
I've used the execfile approach in my settings.py like so:
# Include any local settings that override the defaults.
try:
execfile('local_settings.py')
# Hack so that the autoreload will detect changes to local_settings.py.
class dummymodule(str):
__file__ = property(lambda self
On Tue, Mar 22, 2011 at 5:17 PM, Carl Meyer wrote:
> Interesting. I would have assumed that the reason is so that code in
> site_settings.py has access to the previously defined values in the main
> settings.py, and can actually modify them (i.e. append to
> MIDDLEWARE_CLASSES or whatnot). With an
On Wed, Mar 23, 2011 at 4:32 AM, Rohan Jain wrote:
> These are some auth settings and models I propose to account for the
> generally
> raised questions for auth.User flexibility.
Two quick points:
Firstly -- the fact that you've given some biographical detail at the
bottom, and that this biogra
I would further add that the goal of any refactor in this area is not to add
a wishlist of enhancements to the existing User model (though that may
happen in tandem), but to truly make the framework extensible/agnostic in a
way which it currently is not.
All the best,
- Gabriel
--
You re
On Wednesday, March 23, 2011 5:10:36 AM UTC+5:30, Russell Keith-Magee wrote:
>
> On Wed, Mar 23, 2011 at 4:32 AM, Rohan Jain wrote:
> > These are some auth settings and models I propose to account for the
> > generally
> > raised questions for auth.User flexibility.
>
> Two quick points:
>
> First
On Wed, Mar 23, 2011 at 10:21 AM, crodjer wrote:
> On Wednesday, March 23, 2011 5:10:36 AM UTC+5:30, Russell Keith-Magee wrote:
>>
>> On Wed, Mar 23, 2011 at 4:32 AM, Rohan Jain wrote:
>> > These are some auth settings and models I propose to account for the
>> > generally
>> > raised questions f
> I also haven't seen any proposals or examples of how I'd use the API as
> an end user - are people going to be able to register serialisers to
> models (since they're apparently tied to specific models anyway)?
There will be different types of serializers like JSONSerializer,
YAMLSerializer, XML
First of all: my native language is not English, so I apologize for
any potential natural language error (or any error at all) below.
After (briefly) reading through the current implementaion as well as
the "Issues to consider" section in the GSoC2011 page on wiki, my
initial observation is that t
It's here!
Django 1.3 has been officially released.
Blog post here: http://www.djangoproject.com/weblog/2011/mar/23/13/
Release notes here: http://docs.djangoproject.com/en/dev/releases/1.3/
Download here: http://www.djangoproject.com/download/
--
"Bureaucrat Conrad, you are technically correc
Congratualations to all involved!
-- Gert
Mobile: +32 498725202
Twitter: @gvangool
Web: http://gert.selentic.net
On Wed, Mar 23, 2011 at 07:15, James Bennett wrote:
> It's here!
>
> Django 1.3 has been officially released.
>
> Blog post here: http://www.djangoproject.com/weblog/2011/mar/23/13
29 matches
Mail list logo
