Hi Ronny, >From my POV breaking those internal APIs slowly and with warnings in place is fine, just like it was done with the "marks" API.
I suspect that the internal Node creation API sees even less usage than marks, so I think it is fine to break it slowly and with proper warnings in place. One thing we should keep in mind is that we need to provide a clear way for users to update their code, as well as state the motivation to why we are changing things. Cheers On Mon, Oct 1, 2018 at 5:39 AM RonnyPfannschmidt < opensou...@ronnypfannschmidt.de> wrote: > Hi everyone, > > yesterday i tried yet again to reshape node structure to allow the > integration of function-definition. > every time i work with something around those structures it becomes > apparent, that its immensely fragile to work within it with backward > compat in mind, > its so deeply cross-related that every time we try something, something > else breaks (just remember the fallout of the introduction of `Package`). > > as such i want to enable iteration and breaking apis in that area since > its simply impossible to sustainable evolve it right now, and im unable > and unwilling to throw away a immense amounts of time to keep everything > surrounding working exactly as is. > > the caveat is, that i expect to be at least 10-15 iterations each doing > a micro-breakage around a completely messy area of the api. > i would like to note that i consider this crisscross de-tanglement as > an absolute necessity to the development of pytest, if we cant detangle > massive debts and messes like that, we should just start over from the > beginning. > > -- Ronny > > > _______________________________________________ > pytest-dev mailing list > pytest-dev@python.org > https://mail.python.org/mailman/listinfo/pytest-dev >
_______________________________________________ pytest-dev mailing list pytest-dev@python.org https://mail.python.org/mailman/listinfo/pytest-dev
