On Friday, March 3, 2017 at 2:30:09 AM UTC-5, Michael Merickel wrote: > > TLDR - You may want to pin 'pyramid_tm < 2.0' until you have a chance to > understand the changes. >
two comments: 1. have you considered marking `pyramid_tm` as end-of-life, and pushing for the new changes as `pyramid_transaction` or some other uniquely different name? 2. it might make sense to have deployment advice recommend people install `pyramid_tm` etc as <2.0 and then <3.0 (or some other number) for future compatibility issues. I've been bitten by large API changes like this before. Not from Pyramid, but other projects where some 3rd party library updates another 3rd party library to an incompatible version. It's a giant pain. -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/pylons-discuss/9d2dba10-f67e-4ca4-a89c-808969fa4202%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
