;
>
> How did you go about using psycogreen.gevent for postgresql async
> behavior? I'm
> On Tuesday, August 21, 2018 at 10:16:03 AM UTC-7, James Addison wrote:
>>
>> On Monday, June 4, 2018 at 6:18:23 AM UTC-7, Andrew Godwin wrote:
>>>
>>> For a while now
On Monday, June 4, 2018 at 6:18:23 AM UTC-7, Andrew Godwin wrote:
>
> For a while now I have been working on potential plans for making Django
> async-capable, and I finally have a plan I am reasonably happy with and
> which I think we can actually do.
>
Andrew,
Out of curiosity, how would thes
For others getting up to speed, prior discussion is
here: https://code.djangoproject.com/ticket/29656. Tim's comment from the
ticket commentary is most instructive, I think:
> I'm not sure if there's a model field in Django where there's a chance for
> two values that could be considered "em
docs.djangoproject.com/en/1.9/ref/databases/#postgresql-notes -
PostgreSQL < 9.1 is not supported. Your options to are to upgrade
PostgreSQL or downgrade Django. Obviously, the former is recommended.
--
[image: photo] James Addison
e: add...@gmail.com
<http://ca.linkedin.com/in/jamesad
In using Marten Kenbeek's URL dispatch rewrite branch, I've found that
using the pattern of defining some site configuration in your settings is
the way to go: it more easily allows you to have URL patterns on multiple
domain/scheme combinations.
I use a dict similar to what Tim has shown, and the
Marten,
As you likely remember, I've been running your code for a few months now,
overall it's been pretty good. I mentioned some time ago that the list of
URLs displayed with `DEBUG=True` when triggering a 404 is sometimes empty,
or partially empty. This still happens for me, and I believe
.
Looking for feedback here. Thanks.
James Addison
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django
I have a model like so:
class Provider(models.Model):
description = models.TextField(default='')
In recent Django 1.9 changes (this did not occur with 1.8.x), this causes
the following traceback:
Performing system checks...
Traceback (most recent call last):
File
"/home/vagrant/.virtu
ranch after 1.9 alpha around September 21). In the meantime, if you want
>> take a look for some simpler tickets to tackle to get a feel for our
>> contribution process, I think that would be helpful.
>>
>> On Tuesday, August 25, 2015 at 2:25:07 PM UTC-4, James Addison wrote:
jango/compare/master...jaddison:gsoc2015_url_dispatcher
[4] https://gist.github.com/jaddison/18dea1bf93767f326aa5
[5]
https://groups.google.com/forum/#!searchin/django-developers/marten/django-developers/IoivPLHJ_nw
and
https://groups.google.com/forum/#!searchin/django-developers/marten/djang
. Marten has been MIA unfortunately. Someone else could
> try to pick it up, but it seems a bit ambitious to complete in the time
> remaining before alpha.
>
> On Monday, August 24, 2015 at 10:02:38 AM UTC-4, James Addison wrote:
>>
>> Hi Marten,
>>
>> I'm just c
Hi Marten,
I'm just curious if this is still on track for inclusion within the Sept 21
Apha feature deadline? I've been using your Django `dispatcher_api` branch
for a new project since I learned of your proposed changes and am excited
to see them in stable Django. There hasn't been any changes
> Hopefully we can add Marten's URLs GSoC project to this list.
>
To me, this would be a killer feature of Django. Marten, if you see this,
know that I'll help you out in testing as best I can - feel free to reach
out!
On Friday, July 17, 2015 at 10:19:38 AM UTC-7, Tim Graham wrote:
>
> Curr
Marten,
Using your *dispatcher_api* branch, I found a few issues - I believe this
is an acceptable place to post them. My apologies if this is not the case.
My use case is this: Using a single Django codebase, I plan to have
www.example.com and my.example.com. 'my' will be https, while 'www' wi
14 matches
Mail list logo
