On 03/14/2016 10:34 PM, treal tv wrote: > I might be misunderstanding you, Simon, but should I not be using Mailman 3 > built with the bundler > if I intend to modify/further build on the code? > > I've been working off one built with the bundler for the last couple months > and it's tolerated the > mods I made without issue but I'd rather switch to source built sooner rather > than later if it's > going to matter in the future. I'm unaware of any real downside to using the repo (unless you are a security fanatic and want stuff tested for a couple of years ^^) You can also use bundler with git repos. You'll just have to do run "python setup.py develop" for mailman in the python3 virtualenv that bundler installs. Note you will want to use the other repos as well, as there might be some incompatibilities.
Now to why you should be using it: In case you want to turn in patches (merge requests) then having a repo is a must. And if you don't plan to turn in patches it's still useful. You can work on another branch than master and whenever upstream has new commits you can rebase them into your branch. That way you stay up to date without too much maintenance _______________________________________________ Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
