Hi, as Adam points out 1.0 is on it's way. My mails were written with that 
knowledge and assumption, sorry for not making this clear. I did actually 
had in mind to wait till it is out of beta -- which is most likely before 
we finished our discussions :D

Cheers,
Florian

On Monday, April 15, 2019 at 9:06:29 AM UTC+2, Adam Johnson wrote:
>
> Lukasz Langa, the developer, said he will tag the first non-beta version 
> in "Early April." https://twitter.com/llanga/status/1106247623802060802 There 
> won't be any significant changes when it leaves beta afaiu.
>
>
> On Mon, 15 Apr 2019 at 08:40, Scot Hacker <scot....@gmail.com 
> <javascript:>> wrote:
>
>>  Just bringing this up for the sake of thoroughness: 
>> NOTE: This is a beta product
>> *Black* is already successfully used by several projects, small and big. 
>> It also sports a decent test suite. However, it is still very new. Things 
>> will probably be wonky for a while. This is made explicit by the "Beta" 
>> trove classifier, as well as by the "b" in the version number. What this 
>> means for you is that until the formatter becomes stable, you should 
>> expect some formatting to change in the future. That being said, no 
>> drastic stylistic changes are planned, mostly responses to bug reports.
>>
>> Many/most of us use it in production settings already, as the AST check 
>> guarantees it isn't going to break anything, but the beta status means you 
>> can't always do a simple `pip install black`, and it means that black's 
>> formatting choices could change. 
>>
>> Does a project as significant as Django want to adopt a beta tool whose 
>> "contract" with its users has not yet stabilized?
>>
>> I heart black and would be happy to see it in Django but wonder if we 
>> should wait a bit to hit 1.0.
>>
>> ./s
>>
>> -- 
>> 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-d...@googlegroups.com <javascript:>.
>> To post to this group, send email to django-d...@googlegroups.com 
>> <javascript:>.
>> Visit this group at https://groups.google.com/group/django-developers.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/django-developers/5d71f95a-1a8a-4db4-a2ac-8a59adde1fb5%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/django-developers/5d71f95a-1a8a-4db4-a2ac-8a59adde1fb5%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
> -- 
> Adam
>

-- 
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 post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/4d5ec068-b06a-4c68-9805-29b00eab7983%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
    • ... charettes
      • ... Florian Apolloner
        • ... charettes
          • ... Emil Madsen
            • ... Florian Apolloner
      • ... Dmitriy Sintsov
        • ... Kye Russell
          • ... Josh Smeaton
  • R... Scot Hacker
    • ... Adam Johnson
      • ... Florian Apolloner
  • R... 'Ivan Anishchuk' via Django developers (Contributions to Django itself)
    • ... Josh Smeaton
      • ... 'Ivan Anishchuk' via Django developers (Contributions to Django itself)
        • ... Josh Smeaton
          • ... Dan Davis
            • ... Tobias Kunze
              • ... Tom Forbes
              • ... Jon Dufresne
            • ... Brice Parent
  • R... Matthias Kestenholz

Reply via email to