On 25/07/2020 13:14, Martin Blais wrote: > On Sat, Jul 25, 2020 at 2:23 PM Daniele Nicolodi <dani...@grinta.net > Would it make sense to have v2 depend on the new project instead that > having the code in two places? beancount v2 setup.py could restrict the > version to (for example) 'beanprice < 2.0' so that incompatible changes > can be pushed to another branch. > > This only requires publishing beanprice to PyPI and declaring the > dependency in setup.py (and merge the patch that removes beanprice from > master to the v2 branch). I can do that if there is agreement about this > way forward. > > > I thought about removing it from v2, and doing the same for report/web, > but I kind-of feel that until v3 has at least a "beta" level base to > work from, it's probably best not to mess too much with v2, current > users should be able to just keep working without having to make changes.
Unless I am missing something, there would not be any user visible change other than one more package downloaded and installed when 'pip install beancount' is run. Cheers, Dan -- You received this message because you are subscribed to the Google Groups "Beancount" group. To unsubscribe from this group and stop receiving emails from it, send an email to beancount+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/3e7cc3bd-2ad9-a789-9057-c12bcd67c5be%40grinta.net.
