[pydotorg-www] Edition request for the WebFrameworks wiki
steve at holdenweb.com
Mon Feb 11 05:57:23 EST 2019
In accord with what’s been said so far. Think of the Wikibeditorial force
as little gnomes, each making small positive changes in their area(s) of
expertise. It isn’t like Wikipedia, and conflict is rare.
Thanks for caring enough to seek editor permissions.
On Mon, 11 Feb 2019 at 08:08, Florimond Manca <florimond.manca at gmail.com>
> Yes, sure, Mats. This is actually my first time as a wiki editor so I’m
> still new to the workflow. Will send an update when I get time!
> > Le 11 févr. 2019 à 02:09, Mats Wichmann <mats at wichmann.us> a écrit :
> >> On 2/10/19 4:01 PM, Florimond Manca wrote:
> >> I just made the change, thanks!
> >> I was wondering — how relevant would it be to create a separate section
> for asynchronous frameworks?
> >> There is actually quite a few of them. Some are in the list already
> (Quart, Sanic, and now Bocadillo) and some not yet (Starlette, Responder,
> Vibora, Japronto, etc.).
> >> Perhaps it would be better to set them apart in a section called «
> Asynchronous frameworks » or similar. I’m not sure whether there should be
> a distinction between fullstack/non-fullstack since all existing async
> frameworks are quite « micro ».
> > Given the "you're either in the non-async world or you're in the async
> > world" nature exposed by your first point, why don't you just go for it?
> > It's a wiki, if people hate it it can just be changed again.
> > Less clear on fullstack/non-fullstack distinction, maybe others have
> > opinions? (or you could elaborate further?)
> pydotorg-www mailing list
> pydotorg-www at python.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the pydotorg-www