On Thu, Mar 10, 2016 at 6:23 PM, William Stein <wst...@gmail.com> wrote: > On Thu, Mar 10, 2016 at 9:20 AM, Erik Bray <erik.m.b...@gmail.com> wrote: >> On Thu, Mar 10, 2016 at 6:10 PM, Jeroen Demeyer <jdeme...@cage.ugent.be> >> wrote: >> I guess more generally what I'm interested to learn more about is what >> the typical development workflow is of people who work regularly on >> Sage... > > One thing it is not right now is: "setup a virtualenv with just the > Sage library" and go at it. I very much wish this was supported, > since a lot of people use SageMathCloud and want to do sage dev, but > it's way too heavy weight. If it were as simple as a virtualenv, it > would be a lot easier.
Same. If all of Sage-the-library's dependencies are provided by the system (a BIG if) then this is all that's really needed to hack on the sage Python package in principle. It would certainly be my preference but that's just because it's what I'm used to, not out of any value judgment (though it's also what most Python developers in general are used to). > So please consider both what the workflow is now, and what it could be > in the future if we were able to expand our developer base. +1 though I wouldn't want to step on too many toes either. I've been on both sides of that before in other projects so I know how it goes... :) -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
