Hi Claude,
Very good point. I am not familiar with the translation process. I think we
would benefit from the linter. It’s not so much a linter in the traditional
sense, since it’s not linting any code. It rather finds small errors in
translations files. Inconsistencies in punctuation, line
Thanks Joe for this proposal. Unfortunately, I fear it does not play well
with our current workflow, where we download files produced by Transifex.
Could you give us an example where an error revealed by this linter could
improve the quality of the resulting translations?
Claude
--
You
FTR I published my own writeup here:
https://blog.yourlabs.org/post/183077442308/django-js-research-report
--
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
> most people currently lean towards a microservice architecture and therefore
> towards flask.
"according to the 2018 JetBrains Developer Survey" and some people.
Why start a project with flask in 2019 instead of Quart which or
Starlette is another question that I suppose is out of the scope of
I don't think that a Docker image would make local development any easier.
I also don't see how that is implied by the reddit post and it's comments.
Looking through the posts, I agree with the assessment, that most people
currently lean towards a microservice architecture and therefore towards
