[sage-devel] Re: Request for advice : upgrading a standard package requires a new package

As Francois said, don't make it more complicated than it really is On Monday, November 30, 2015 at 11:47:17 PM UTC+1, Emmanuel Charpentier wrote: > > Bonus question : how to package rpy2 to signal that it depends on > singleispatch ? > Put it into build/pkgs/rpy2/dependencies -- You received

Re: [sage-devel] Request for advice : upgrading a standard package requires a new package

The policy that I, Volker and Jeroen (I think) have followed in those case - and it happened a lot while upgrading the various versions of ipython - is to include the new package as standard in the upgrade ticket. It is the only non-crazy option. Either you leave a stall package because you can

[sage-devel] Request for advice : upgrading a standard package requires a new package

Dear list, I wish to upgrade the rpy2 python package to 2.7.4 : our antique version (2.3.8) no longer allows to use the ipython interface in the Jupyer notebook. I've checked that this upgrade is enough to get a functional %R (and %%R) interface in the Jupyter notebook. However, I am told

[sage-devel] Funding idea: selling hardware

Hello: In a recent local spanish Sage meeting, some folks from the University of Vigo told us about their Sage setup for the classroom using a laptop as a sage server. Their wireless at some classrooms is not good enough, so they would bring the laptop to the classroom, create and share a local ne

[sage-devel] Re: Who uses SAGE64

On Monday, November 30, 2015 at 2:18:09 AM UTC+1, John H Palmieri wrote: > > > > On Sunday, November 29, 2015 at 1:47:26 PM UTC-8, Volker Braun wrote: >> >> François asked me whether we still use the SAGE64 sections that are >> copy-pasted into many spkg-install files; All I know is that no buil