> Even so, there are mitigations to the firehose effect, including, but not
> limited to digests
I accidentally signed up with divest turned on for this list first. I got five
digests in so many hours and I couldn’t figure out how to respond to individual
threads. It’s a terrible choice and
On Wed, Sep 19, 2018 at 7:49 AM Franklin? Lee
wrote:
>
> On Tue, Sep 18, 2018 at 8:21 PM James Lu wrote:
> >
> > > Is that really an issue here? I personally haven't seen threads where
> > > Brett tried to stop an active discussion, but people ignored him and
> > > kept fighting.
> > Not
Just an observation. I've been a member of this mailing list since
(literally) five days ago and I am receiving a busload of emails.
I'm a member of Stackoverflow and I visit the Q site daily... and I
hardly ever receive emails.
I suspect Discourse would be a good match for these discussions
>
> Most of the real decisions are actually taken
> outside of it, with more direct channels in the small groups of
> contributors.
>
It would be very nice if there was more transparency in
this process. The language is better if more subjective
personal experience heard- but to make that happen,
Oh wow, Google Groups is actually a much better interface.
Any better forum software needs a system where people can
voluntarily leave comments or feedback that is lower-priority.
I'm not sure if Discourse has this, actually. Reddit comments
are extremely compact as are Stack Overflow comments.
Le 19/09/2018 à 15:28, Chris Angelico a écrit :
> On Wed, Sep 19, 2018 at 11:23 PM Michel Desmoulin
> wrote:
>> - A is telling B this is a bad idea. It should be easy to tell if the
>> person is experienced or not. You probably don't want to interact the
>> same way with Victor and Yury, that
Le 19/09/2018 à 00:37, James Lu a écrit :
>> Is that really an issue here? I personally haven't seen threads where
>> Brett tried to stop an active discussion, but people ignored him and
>> kept fighting.
> Not personally with Brett, but I have seen multiple people try to stop the
> “reword or
On Tue, 18 Sep 2018 18:37:09 -0400
James Lu wrote:
> * The mailing list is frankly obscure. Python community leaders and package
> maintainers often are not aware or do not participate in Python-ideas. Not
> many people know how to use or navigate a mailing list.
> * No one really promotes
>> I'd suggest using parso to do it. It's a really great library to write such
>> transformations.
>
> Ah. It wasn't clear what your destination was, so I thought you were
> talking about doing the translation itself using parso. But yeah, grab
> one of these sorts of parsing libraries, do the
On Wed, Sep 19, 2018 at 4:52 PM Anders Hovmöller wrote:
>
>
> > How about this: Have a script that runs over your code, looking for
> > "translatable f-strings":
> >
> > _(f'Hi {user}')
> >
> > and replaces them with actually-translatable strings:
> >
> > _('Hi %s') % (user,)
> > _('Hi
> How about this: Have a script that runs over your code, looking for
> "translatable f-strings":
>
> _(f'Hi {user}')
>
> and replaces them with actually-translatable strings:
>
> _('Hi %s') % (user,)
> _('Hi {user}').format(user=user)
>
> Take your pick of which way you want to spell it.
On Wed, Sep 19, 2018 at 3:55 PM Steve Barnes wrote:
> Surely the simpler solution is to specify in I18n any items within
> un-escaped {} pairs is excluded from the translation, lookups, etc., and
> that translation needs to take place, also leaving the {} content alone,
> before f string
Le mar. 18 sept. 2018 à 13:39, Tobias Kohn a écrit :
> Hello Everyone,
>
> Please excuse my being late for properly responding to the last thread on
> "Pattern Matching Syntax" [1]. As Robert Roskam has already pointed out at
> the beginning of that thread, there has been much previous
13 matches
Mail list logo
