I have no idea how I've done this, twice.
On Feb 10, 2:16 pm, Alex Gaynor wrote:
> On Thu, Feb 10, 2011 at 5:14 PM, David Cramer wrote:
> > We're going to be deploying a backwards incompatible change to all
> > "since" values in the API. Any endpoint which accepts this parameter
> > to use as a
On Thu, Feb 10, 2011 at 5:14 PM, David Cramer wrote:
> We're going to be deploying a backwards incompatible change to all
> "since" values in the API. Any endpoint which accepts this parameter
> to use as a form of range pagination will now include the value sent,
> as well as values before or af
We're going to be deploying a backwards incompatible change to all
"since" values in the API. Any endpoint which accepts this parameter
to use as a form of range pagination will now include the value sent,
as well as values before or after it (depending on the order).
For example, in the original
On Thu, Feb 10, 2011 at 1:54 PM, Tom Evans wrote:
> I've updated the ticket with a patch against trunk implementing uuid
> session keys
One of the reasons why it was coded like this was because you can not
tell the difference in the cache backend between a key collision and
memcache being una
On 10 February 2011 08:15, Russell Keith-Magee wrote:
> 2011/2/5 Łukasz Rekucki :
>> With Django 1.3 almost out, I would like to ask, what's the current
>> deprecation plan of old Python versions (namely 2.4 and 2.5). The
>> major argument against dropping 2.4 was RHEL support. RHEL6 seems to
>> s
On Thu, Feb 10, 2011 at 12:45 PM, Russell Keith-Magee
wrote:
> The DB model for cache keys provides for 40 characters, so we can
> certainly store a UUID. If you can provide an implementation and can
> demonstrate that it won't be prone to key collisions and won't impose
> any computational limits
On 10 February 2011 07:29, Russell Keith-Magee wrote:
> On Thu, Feb 10, 2011 at 5:45 AM, Thomas Adamcik wrote:
>> On Wed, Feb 9, 2011 at 12:00 PM, Russell Keith-Magee
>> wrote:
>>> Another interesting, but more complicated opportunity in this area
>>> would be asynchronous database calls [1], wh
Hi Ben,
On Thu, Feb 10, 2011 at 4:48 AM, Ben Ripkens
wrote:
> Hello Django developer community,
> my name is Ben Ripkens and I'm planning to contribute to the Django
> project through this years Google Summer of Code.
I'm replying because I'm the one that created that page mostly as a initial
dr
On Thu, Feb 10, 2011 at 3:48 PM, Ben Ripkens
wrote:
> Hello Django developer community,
> my name is Ben Ripkens and I'm planning to contribute to the Django
> project through this years Google Summer of Code. I found the ideas page
> for 2011 [1] and even though it seems not publicly available I'
On Thu, Feb 10, 2011 at 7:36 PM, Tom Evans wrote:
> On Thu, Feb 10, 2011 at 6:56 AM, Russell Keith-Magee
> wrote:
>> However, my concern here is that for any value of N, there will be
>> some level of traffic that will render that N insufficient. I'm not
>> fundamentally convinced that allowing N
Hi again
@benjamin
Django-command-extension is a really great tools but ipython is a robust
python shell with internal debugger autho completer and some many
features, there are many situation that runserver_plus does does not
come handy, also terminal is a great friend of a developer you have
te
Hello Django developer community,
my name is Ben Ripkens and I'm planning to contribute to the Django
project through this years Google Summer of Code. I found the ideas page
for 2011 [1] and even though it seems not publicly available I'm curious
whether the mentioned ideas are up to date, availab
`runserver_plus` from django-extensions together with Werkzeug's debugger is
a great tools,
but ipython console is more greater! Usualy than I work with site on dev
server, I have already
opened in IDE the project sources.
On Thu, Feb 10, 2011 at 2:19 PM, Benjamin Wohlwend wrote:
> Hi,
>
> On Th
On Thu, Feb 10, 2011 at 11:36 AM, Tom Evans wrote:
> If this sounds amenable, I can code up a patch for the ticket.
>
Indeed, I was piqued, so did it anyway. Running with it now.
Cheers
Tom
--
You received this message because you are subscribed to the Google Groups
"Django developers" group
On Thu, Feb 10, 2011 at 6:56 AM, Russell Keith-Magee
wrote:
> However, my concern here is that for any value of N, there will be
> some level of traffic that will render that N insufficient. I'm not
> fundamentally convinced that allowing N to be configurable will
> actually fix the problem. I'd b
I'm not a fan of one-size-fits-all debugging tools. The last several replies
clearly show the variety of preferences people have for the already-existing
options. Adding a setting that allows you to replace the debugging module
also implies the replacement modules support a common API, which may
Hi,
On Thu, Feb 10, 2011 at 8:44 AM, Matteius wrote:
>
> What I want to see (and possibly the closest I've seen it with was a
> video on the django_command_extensions) is an interactive debugger
> built into my test-dev server so I can have break pts, switch logic
> values in place, etc. dynamica
I agree with idea, but wish, that it would be implemented not only in
runserver, but also in test command:
$ python manage.py runserver --debug
$ python manage.py test --debug
I really missing this functionality, which is implemented and works
very well in nose:
http://packages.python.org/
18 matches
Mail list logo
