d
they're working on something, and if it allows seamless migration, that'd be
great. That said, if they take more than a month or two, we should just change
it and get it over with.
Andrew
On Tue, Jun 16, 2020, at 12:59 PM, Adam Johnson wrote:
> On the branch rename, right now I&#x
ones I
work on. Migrations isn't meant to only be "makemigrations" and the model-based
approach; there's also an underlying SQL application and dependency ordering
engine that can be used standalone.
Andrew
On Thu, Aug 6, 2020, at 1:27 PM, Paolo Melchiorre wrote:
> HI
that would be my suspicion as to why this
would be structured this way in my original code. As you say, the optimiser has
improved in the years since, but I don't think you can optimise away the
circular reference problem?
Andrew
On Sat, Sep 19, 2020, at 3:20 PM, Silvio J. Gutierrez wrote:
Hey guys, I'd like to contribute to the effort to make Django more async
capable. I've started to write an aioredis based cache backend based on
django-redis, but I noticed the BaseCache in Django is still all
synchronous basically.
I was wondering which backends I should make async capable and
r all
of them and if everything can be made to work regardless of what mode (sync or
async) it's in; hopefully there's a lot less long-lived-connection issues than
in the ORM, say.
Andrew
On Sat, Sep 26, 2020, at 3:56 PM, Adam Johnson wrote:
> Hi Andrew
>
> I don't be
Hey Adam and Andrew,
I can definitely make the naming scheme something like get_async() rather
than just get().
> This section specifically says that the default implementations will back
onto the sync methods by default, so built-in cache backends won't need to
all be converted
Cool, thanks for the clarification. One thing I noticed while programming
the test cases (so WIP is
here: https://github.com/Andrew-Chen-Wang/django-async-redis) is that it's
not really fun having to type out get_async since autocomplete. If a dev
knows that they'll be using an awa
.
I think right now I would prefer get_async all things considered, since I don't
think autocomplete is necessarily easier either way, but I'm open to
suggestions.
Andrew
On Sun, Sep 27, 2020, at 6:03 PM, Andrew Wang wrote:
> Cool, thanks for the clarification. One thing I notice
Hi all,
1.5 weeks ago, I posted that I was interested in making Django's cache
async. Just here to report that the package for django-async-redis is on
pypi and the repo is
here: https://github.com/Andrew-Chen-Wang/django-async-redis. Please test
it out. I have only tested it on a
elp debug it further.
Andrew
On Tue, Oct 13, 2020, at 10:37 AM, Adam Johnson wrote:
> I'd like to see what Andrew thinks on this.
>
> I had a thought that the issue you're seeing may be related to a dependency
> of your project creating/destroying event loops in the backgr
pervise enough forum API access for you to try it,
Tom.
Andrew
On Thursday, October 29, 2020 at 9:23:45 AM UTC-6 carlton...@gmail.com
wrote:
> I don’t have any controls here. I’m pretty sure Florian would be the most
> likely candidate. (No doubt it’s Jacob.)
>
>
>
--
You recei
I have been moving house this week (plus, yknow, the election) so I haven't got
anything done, but hope to poke at it early next week!
Andrew
On Sun, Nov 8, 2020, at 4:34 AM, Carlton Gibson wrote:
> Hi Tom and Andrew.
>
> This week has been *busy *(shall we say) I know — can I
ite my own script to mash the APIs over HTTP)
Andrew
On Sun, Nov 8, 2020, at 2:36 PM, Andrew Godwin wrote:
> I have been moving house this week (plus, yknow, the election) so I haven't
> got anything done, but hope to poke at it early next week!
>
> Andrew
>
> On Sun, Nov 8,
I agree we should not be quite so beholden to our existing Python version
policy - that was mostly to get us out of the early 3.x era. Now things are
more stable, I'd support a policy that is much more like "any stable version of
Python currently out there and supported".
found here:
https://github.com/Andrew-Chen-Wang/SPA-with-httponly-sessions .
The original purpose of this thread was for SPA development, not really for
JWTs. I'm a maintainer at SimpleJWT, a repository that almost all tutorials
use to show React/SPA/JS Frameworks and Django integration. I
re is wide adoption
for webpack, because of the JS bundles continuously growing (being a huge
turn-off once you have a semi-production-grade SPA repository), I proposed
a moderate idea:
To fix this, I'm going to develop a middleware as described in issue #3
here:
https://github.com/Andrew-Che
alled and can have
everyone developing on it do something at once, you can just do it via a
complete migration reset and be happy. Squashing is for a very specific
backwards-compatibility scenario that, I suspect, many Django projects
developed internally are not in.
Andrew
On Tue, May 11, 2021,
desconstructions, usually).
Andrew
On Sat, Sep 18, 2021, at 9:06 AM, Christian González wrote:
> Hi,
>
> before I issue a bugreport, I'll ask here first.
>
> On
> https://docs.djangoproject.com/en/3.2/topics/migrations/#adding-a-deconstruct-method
> I can read that decon
s used?
Cheers,
Andrew
--
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-developers+unsubscr...@googlegroups.com
of the Django test suite is designed for synchronous
db engines, so the default alias database engine will switch around a bunch
of times.
3. Implement a test decorator that switches the default alias connection.
Lemme know if that's confusing.
Thanks,
Andrew
--
You received this message b
#x27;: 'async' }, 'async': { 'ENGINE':
'django.db.backends.aiosqlite', }, }
I'm not sure if either of these options are possible due to sqlite being
tested in memory though.
On Monday, January 31, 2022 at 6:48:13 PM UTC-5 Adam Johnson wrote:
>
this at all as JOINs or
cross-table queries in one piece of code aren't allowed, but they probably
already have plenty of expertise in this area. We also need to give
consideration to how it will interact with multiple database support, and
third-party solutions to things like sharding.
Andrew
#x27;t let people unwittingly
wander into giant changes. The downside is that it does add slightly more
friction to the upgrade process.
Andrew
On Thu, Aug 17, 2017 at 2:36 PM, Kenneth Reitz wrote:
> I have opened a pull request:
>
> https://github.com/django/django/pull/8924
>
> An
see any other solutions that aren't settings doing
spooky-action-at-a-distance to primary keys, and that's something I really
don't want to see.
Andrew
>
> On Thu, Aug 17, 2017 at 02:43:07PM -0700, Andrew Godwin wrote:
>
>> To elaborate on the solution we eventual
to plug-and-play with the ModelForm framework. So my
question is:
Is there any particular reason that save_form_data does not have some
default behavior for through models?
Cheers,
Andrew
--
This message has been scanned by E.F.A. Project and is believed to be clean.
--
You received thi
patch would definitely help clean up the code
in my situation.
I'll patch our test server and see if everything runs smoothly and keep
an eye that pull request.
Cheers,
Andrew
On 1/16/2018 8:39 AM, Collin Anderson wrote:
Hi Andrew,
Would allowing set() for through models help in
7;ModelBackend' in favour of something like
'ModelPermissionOnlyBackend'
Additionally if Mehmet wanted to finalize an API that allowed users to
specify a subset of backends to check against, this approach would
support that.
Cheers,
Andrew
On 1/17/2018 2:45 AM, Carl
ic on this.
Regarding an API that will allow picking and choosing I already have
some ideas, but I think Carlton made an excellent point that that is
another discussion all together.
Cheers,
Andrew
On 1/17/2018 5:34 PM, Mehmet Dogan wrote:
Andrew,
Thank you for the input. Having optio
,
Andrew
--
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-developers+unsubscr...@googlegroups.com.
To po
the backend whose
behaviour it requires.
```
class RolesBackend(PermissionAuthorizationBackend):
def has_perm(self, user_obj, perm, obj=None):
...
for delegate in delegates:
if super(RolesBackend, self).has_perm(user_obj, perm, obj):
return True
Hey Collin,
I posted a new PR: https://github.com/django/django/pull/9609
Let me know what your thoughts are.
I also updated the ticket.
Cheers,
Andrew
On Thursday, January 18, 2018 at 6:57:06 AM UTC-8, Collin Anderson wrote:
>
> Hi Andrew,
>
> Sure, do you want propose som
I would very much welcome a narrative tutorial like the Django docs - I did
not have the time to personally write and QA one before the 2.0 release,
unfortunately. I'm happy to help out if you want to email me personally to
discuss!
Andrew
On Sun, Feb 4, 2018 at 10:39 PM, David Foster
Hi Daniel,
It was something I was going to do myself once I had the time and the
release support for 2.0 dies down, but if you want to take a crack at it,
please do (I am more than happy to consult where I can).
Andrew
On Sat, Feb 17, 2018 at 1:13 PM, Daniel Gilge wrote:
> Hi,
>
>
aging/QA
deploys, like many environments do).
I think it would be a fine addition as an optional third-party tool, but
it's not something that really makes sense to include in Django at this
point I think.
Andrew
On Mon, Feb 19, 2018 at 10:05 PM, djrobstep wrote:
> Hi all,
>
> Some
o your own performance measurements with your
environment and your code to work out what you can do. I would say,
however, don't run "runserver" in production!
Andrew
On Mon, Mar 19, 2018 at 10:54 AM, John Carrell
wrote:
> Can I please ask a clarifying question?
>
> You
ere if you are interested.
Andrew
On Tue, Mar 20, 2018 at 2:30 PM, Jonathan Stray
wrote:
> Can anyone offer a brief account of how Channels uses threads to service
> multiple requests?
>
> My understanding is that there are multiple workers, and I imagine each is
> a thread whi
lain if it's not working right (even though that thing is on the
receiving side not the sending side).
Andrew
On Sat, Mar 24, 2018 at 4:31 AM, Josh Smeaton
wrote:
> I've finally had the chance to use channels for a project (hack day
> multiplayer game - hope to release and bl
nice
facade in terms of keeping them low maintenance, and also in letting people
solve dependency/versioning/schema upgrade issues in the way that fits them
best.
Andrew
On Sun, Mar 25, 2018 at 4:08 PM, Josh Smeaton
wrote:
> I see - some kind of python type that can be shared amongst c
;id", "test_app_related"."field" FROM "test_app_
related" INNER JOIN "test_app_main" ON ("test_app_related"."id"= "test_app_
main"."related_id") INNER JOIN "test_app_main" T3 ON ("test_app_related&qu
Thank you all for the replies.
@Josh Smeaton
Essentially yes; specifically I was wondering whether I was failing to
consider behaviour that couldn't be modeled via a Q object, since as you
mention the current
https://docs.djangoproject.com/en/2.0/topics/db/queries/#spanning-multi-valued-relati
nd I would love to hear what
you have to say.
Andrew
--
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 d
eventually render different parts of the template concurrently, i.e
> example each iteration of a for loop could be it’s own future resolved
> independently, but this is likely a pipe dream.
>
That would very much be a long-term thing, and honestly something I might
consider handing off
al grant.
Jordan:
I'm not sure how we're going to develop this yet, but it'll likely be a
branch in the main Django repo once this proposal is approved (there's
still a little while before that happens - there needs to be consensus here
and/or a technical board vote).
Andre
in is going to be very beneficial.
The aiomysql package implemented everything in pure Python, as well - it's
possible that similar would be needed for full async PostgreSQL support,
where the non-compiled speed reduction might be outweighed by the
parallelism improvements.
Andrew
--
Y
Hi - this mailing list is for the development of Django itself. You already
posted on django-users (the right one) - please don’t double-post!
I’ll get around to replying to that other one in a day or two.
Andrew
On Sun, 24 Jun 2018 at 18:36, wrote:
> Hi I am deploying a website with a l
be sure that I've not
missed something, like considerations for other databases, or other uses
of `cast_db_type` that mean it can't return 'integer'.
Full details of the route to this problem are below.
Cheers,
Andrew
I ran into it using django-guardian's ob
Hi, this is the mailing list for the development of Django itself. I
suspect you will instead want to ask a question like this to the
django-users list!
Andrew
On Fri, Jul 13, 2018 at 5:37 AM Piotrek eF
wrote:
> Hello,
>
> Normally, when I launch runserver, and login to admin site, I
Just to say that I've reopened the original issue in question as it's clear
now this needs to be fixed. I won't be able to get to writing a fix for a
bit, though, so if someone else wants to they should.
Andrew
On Tue, Aug 28, 2018 at 5:41 AM John Obelenus wrote:
> Just fin
f the most complicated
code in migrations won't be tested properly.
Andrew
On Mon, 8 Oct 2018, 00:59 Ian Foote, wrote:
> Hi all,
>
> On my pull request (https://github.com/django/django/pull/10406)
> refactoring how Django creates database constraints I introduced a
> depend
ople build that sort of
stuff.
Andrew
On Wed, Nov 21, 2018 at 11:48 AM Brylie Christopher Oxley
wrote:
> Hello,
> I have been developing with Meteor.js for about four years now. One really
> nice aspect of Meteor is that it streams data to the client, which in turn
> updates the templ
nal deadline for this is two weeks, on February 1st. If you want to
help out, please feel free to reply either here or get in touch with me
personally to chat about what's involved.
Andrew
--
You received this message because you are subscribed to the Google Groups
"Django developers
y and I'll outline
what's needed.
Andrew
On Thu, Jan 17, 2019 at 10:10 AM Nasir Hussain
wrote:
> Hi andrew, I can help in maintaining the projects. Kindly let me know what
> are the next steps.
>
> Thanks
>
> On Thu, Jan 17, 2019, 11:07 PM Andrew Godwin
>> Hi all,
&
On Sat, Jan 19, 2019 at 12:13 PM Carlton Gibson
wrote:
> Hey Andrew.
>
> I've been thinking a lot about this. You clearly shouldn't be maintaining
> Channels single-handedly indefinitely.
>
> I know Channels started out separately, but, it's time to think abou
On Mon, Jan 21, 2019 at 4:34 AM Michael Martinez <
writemichaelmarti...@gmail.com> wrote:
> Hi Andrew
>
> To me, Websockets is the defining use case for using Django Channels. From
> a user POV, saying that Channels is focused on the wrong problem
> (websockets) is like
tching all the repos come Feb
1st, and barring positive confirmation someone else is going to actively
take over I'll put up notices on all the projects that they are actively
unmaintained apart from security issues.
Andrew
On Thu, Jan 17, 2019 at 10:06 AM Andrew Godwin wrote:
> Hi all,
for now, so if you really need me try that, but I may turn
that off if it turns out to be too much.
Thanks all who came forward. I'm hopeful that things can be kept going!
Andrew
On Wed, Jan 30, 2019 at 2:18 PM Andrew Godwin wrote:
> Just to update on this - nobody has individually come
Django. Adding "git clean" to the script is probably good enough,
but I might be tempted to make a script where you pass it a commit hash and
it checks it out to a fresh temporary directory and packages from there?
Andrew
On Mon, Feb 11, 2019 at 8:28 AM Carlton Gibson
wrote:
> Hi
is commit" button to enable much easier browsing
of files prior to it.
For that reason, I am +1 to using the Black code formatter.
Andrew
On Sun, Apr 14, 2019 at 10:22 AM Curtis Maloney wrote:
> So to summarise the discussion so far:
>
> 1. automated code formatting will be a great b
teeth into, as we
can then start making all the other parts of Django async-capable as a
parallel effort.
Reviews and comments on the PR are encouraged; I want to make sure this is
not going to hurt existing sync Django when it lands, and that it's a
useful stepping stone towards async in view
es long, we might want to consider a
better avenue for constructive feedback.
Andrew
On Tue, Apr 30, 2019 at 12:31 PM Christian González <
christian.gonza...@nerdocs.at> wrote:
>
> Am 30.04.19 um 14:28 schrieb 'Laurens A. Bosscher' via Django developers
> (Contributions
>From my read this also looks like it would make the auto-reloader able to
work a lot better with an async-capable server, so I would be in favour
given that is likely in the future as well.
Andrew
On Tue, Apr 23, 2019 at 9:33 PM Ramiro Morales wrote:
> Hi all,
>
> I had a stab a
So, it looks like most of the comments on this PR have happened and been
resolved - unless anyone has any objections, I will merge it in after a
couple more days (just in time for PyCon US).
Andrew
On Wed, Apr 24, 2019 at 1:50 PM Andrew Godwin wrote:
> Hi everyone,
>
> Just wanted
re means we get to skip writing this up, and from
here on out it becomes much more of a new feature than merely adding safety
and a new handler.
Andrew
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
This is quite unrelated to frontend - I'll explain more of the impact and
potential impact in the DEP when I write it up.
Andrew
On Wed, 1 May 2019, 08:30 Elad Yaniv, wrote:
> Exciting stuff!
> does this mean that django 3.0 COULD compete with frontend js frameworks
> ? (ang
y somewhere between
those two that works.
Thanks for taking the time to read through!
Andrew
--
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 fro
or synchronously, that's
fine - it takes literally zero extra effort to go either way".
This is why I propose in the DEP that we do the view layer first, and then
move onto the ORM as a second wave.
Andrew
On Thu, May 9, 2019 at 12:29 PM Patryk Zawadzki wrote:
> I'm not s
t not as part of
this async push.
Andrew
On Thu, May 9, 2019 at 12:56 PM Patryk Zawadzki wrote:
> That said, I also think it's important to allow the ORM to support both
>> modes in the long term. I truly believe the best way to be able to write
>> async code is to _have the
On Thu, May 9, 2019 at 1:04 PM Aymeric Augustin <
aymeric.augus...@polytechnique.org> wrote:
> Hello Andrew,
>
> Thanks for your work putting together this plan. Within our constraints,
> it's a good plan.
>
> Regarding templating, I would say it isn't a priori
own research and proposal, probably, but it might be a nice way out of the
initial thing of requiring select_related. I just don't know enough about
how that might cascade down the ORM internals to judge it at this point!
Andrew
--
You received this message because you are subscrib
he ORM so people can't screw up by accident. It would be quite easy to
extend this to enforcement on both the sync and async versions - there's
maybe an edge case that you can call an async function from a thread you
have not started an event loop in _yet_, but I'd rather see if and when
ing on an async ORM that works within Django?
>
It is indeed encode/databases!
Andrew
--
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 f
on in the DEP that
says why we can't do it in a separate package, but basically, the changes
required to Django are too deep to do separately (or even as a long-running
fork).
Andrew
--
You received this message because you are subscribed to the Google Groups
"Django developers (Co
stin, for his work on writing and updating the
DEP!
Yours in auto-formatting,
Andrew
--
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
One quick clarification - when I said "stable (1.0)" release, I in fact
meant the first release that the Black project officially marks as stable.
Black doesn't use versioning that would result in a stable release being
called 1.0, as far as I know, given they are on 19.3b0 rig
On Mon, May 13, 2019 at 4:31 AM Tobias Kunze wrote:
> Hi Andrew (and everybody following the discussion, of course),
>
> First off, thank you for your work here. DEP9 is an excellent technical
> document, and it was as easy and pleasant to read as a document of this
> scope a
writing up a funding plan for this, including
various options for how we can pay people for their work.
Andrew
On Tue, May 14, 2019 at 2:55 AM Andrew Godwin wrote:
>
>
> On Mon, May 13, 2019 at 4:31 AM Tobias Kunze wrote:
>
>> Hi Andrew (and everybody following the dis
p consistency
with Python core to lower the workload. If Python core turned around and
blessed greenlets and gevent as the chosen async solution, I'd change my
mind, but I haven't seen any evidence of that over many years.
Andrew
--
You received this message because you are subscr
one (
https://twitter.com/_tomchristie/status/1005001902092967936) using Python
asyncio/ASGI - and see that it does make a difference. Obviously it doesn't
matter for all deploys, but I believe it matters for the majority of site
architectures as they scale up.
Andrew
--
You received this message
ug and say
that Python async isn't ready. However, I've been working with it for the
last four years, including on several very large deployments, and there are
some direct benefits that I believe we can get without making things a lot
more complex, even inside Django.
Andrew
--
You
The DEP is drafted and in the DEPs repo, and awaiting approval by the
freshly-elected Technical Board once I submit it. In the meantime, we
landed the ASGI patch, as well.
Andrew
On Tue, Jun 25, 2019 at 3:30 PM Chris Barry
wrote:
> Hey all,
>
> Just wondering what the future of this i
e.g.
migrations) rather than direct file access (like templates).
It would be nice to investigate this a bit more, though. If we can get
Django compatible, or work with PyOxidiser if we find a reasonable
workaround they could implement, it would be great.
Andrew
On Thu, Jun 27, 2019 at
dules.
Andrew
On Thu, Jun 27, 2019 at 2:01 PM Peter Baumgartner
wrote:
> The big issue I see is that a resource must reside directly in a
> Python module. You can not load a resource from a child directory,
> e.g. I can load "index.html" from the Python module
> "myproj
uture async work.
If you are interested in helping with fundraising, then please get in touch
with me directly; I have some ideas about how to structure it, but I could
do with some people to help out. Otherwise, stay tuned for more information
about how to get involved contributing and what to work
I'll ask permission and then summarise the points raised back out here!
Andrew
On Sun, Jul 21, 2019 at 1:01 PM Jacob Kaplan-Moss
wrote:
> Congratulations, and great news!
>
> I hope the TB will consider sharing details and/or a summary of the "long
> and involved vot
On Sun, Jul 21, 2019 at 1:11 PM Ehigie Aito wrote:
> Django 3.0?
>
Django follows time-based releases; what's in Django 3.0 will depend on
when we can get it landed. At the moment I am optimistic something will
make it in, but I make no promises!
Andrew
--
You received this mess
oard, this is by far the most detailed a vote has ever gotten, and
I can only apologise to the incoming board for springing this on them right
after an election!
If anyone on this list would like to continue to talk about the above, or
if a Board member wants to bring their conversation out here, y
I agree too. Let's change it.
Andrew
On Sat, Jul 27, 2019 at 4:03 AM Markus Holtermann
wrote:
> Easy: +1 from me as well for reasons state before.
>
> /Markus
>
> On Sat, Jul 27, 2019, at 6:15 PM, Adam Johnson wrote:
> > +1 from me too for the reasons that Aymeric sta
y hard to scale - it needs
stateful storage to aid in transferring connections, and this means it's
really hard to have a single method that will work for everyone. Having
"one right way to do it" is sort of a necessary prerequisite to having
something in Django, and I just don't feel
t the question I'd really want everyone
to answer is if it's worth the porting effort. I suspect the answer is yes,
but this does need a process DEP and some discussion, and maybe also
looking at what cpython are doing and comparing and contrasting.
Andrew
On Wed, Aug 7, 2019 at 4:12 AM
with an email filter
as I do now!), and honestly the same thing for django-users. That said, I
also recognise that diluting the support/discussion pool is not exactly an
attractive idea, which is why I'm asking for input!
Thanks,
Andrew
--
You received this message because you are subscr
ense I am describing - one that
has categories, editable posts, and the ability to selectively get email
for certain categories or threads rather than all-or-nothing. The Groups
forum interface is more just an online mailing list interface, with all the
problems of the underlying list model.
Andrew
t, though my impression
is that it's relatively easy since he had it up before I'd got off the
plane back to the US. Not sure about the djangoproject.com login situation
- we need to investigate how flexible the plugin system is, and it might
need OpenID on the Django end.
Andrew
--
You
oogle Groups is probably
going to be around for a long time).
Andrew
On Monday, August 12, 2019 at 4:04:23 AM UTC-5, James Bennett wrote:
>
> I'm not necessarily opposed to this, but I am a bit skeptical of the
> long-term archival utility of forums, in large part due to my experience a
Another point has been raised to me by someone off-list - adding a forum
would significantly increase the surface area that the Code of Conduct team
have to cover (and potentially become one of the biggest time sinks
required), so we need to consider them in any decision.
Andrew
On Mon, Aug 12
ck thread over in the forum (
https://forum.djangoproject.com/t/forum-feedback/17/).
See you there!
Andrew
--
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
I agree - we need to communicate that ASGI support does *not *mean you can
start writing async def views. I think we should put a big disclaimer to
that effect next to it in the release notes and say it should be coming
next release.
Andrew
On Mon, Oct 14, 2019 at 5:45 PM Josh Smeaton wrote
handling, so I don't think I'd want to throw it away and
adopt WSGI 2 directly if it came along, but Django would definitely keep a
direct-WSGI mode for that as it always has.
Andrew
On Mon, Jan 4, 2016 at 9:14 AM, Marc Tamlyn wrote:
> Hi Cory,
>
> [Disclaimer - I don't s
diculously slow sometimes.
Andrew
On Thu, Jan 7, 2016 at 2:03 PM, Aymeric Augustin <
aymeric.augus...@polytechnique.org> wrote:
> As far as I understand, the CPU cost comes from generating a full set of
> model classes for each step of the migration history. That’s consistent
>
x27;s only because I'm able to do the work
now and wait to get paid for it later; I don't expect the same of other
contributors.
Andrew
On Fri, Mar 4, 2016 at 3:58 PM, Chad Paulson wrote:
> I was happy to read that part of the Mozilla Open Source Support program
> funding that w
addition and tweaking some imports.
Andrew
On Sat, Mar 5, 2016 at 4:44 PM, Tim Graham wrote:
> Hi Andrew,
>
> What's your thinking about whether or not any of this will make it into
> 1.10? The alpha is scheduled for May 16.
>
> On Saturday, March 5, 2016 at 2:40:05 PM UTC-5, An
401 - 500 of 630 matches
Mail list logo
