Hi Marc,
On 2017-07-27, Marc Masdeu wrote:
> @Simon maybe it would help the OP if you elaborated on why the group
> cohomology code was not included in the standard Sage...
1. It depends on an optional package with GPL-compatible licence
at build time and on an optional package with GPL-inco
On Friday, July 28, 2017 at 1:04:37 AM UTC+9, Travis Scrimshaw wrote:
>
> ... it is very easy to develop new code within Sage directly. I do this
> all the time, and sometimes this is the only way because you need to modify
> some parts of Sage. It also makes it easier to submit it to trac, whi
On Thursday, July 27, 2017 at 9:27:28 AM UTC-5, Marc Masdeu wrote:
>
> @Simon maybe it would help the OP if you elaborated on why the group
> cohomology code was not included in the standard Sage...
>
> @Nikhil I would suggest that you concentrate in writing useful code in
> ergodic theory. How
@Simon maybe it would help the OP if you elaborated on why the group
cohomology code was not included in the standard Sage...
@Nikhil I would suggest that you concentrate in writing useful code in
ergodic theory. How to distribute it is secondary, IMO. For ease of
development, you definitely do
Hi Travis,
On 2017-07-25, Travis Scrimshaw wrote:
> There is no discussion about why separate packages: only suggestions about
> doing it without mentioning any of the advantages or disadvantages. Yes, my
> wording is (heavily) loaded, but I did give an advantage to developing a
> separate pac
On Monday, July 24, 2017 at 6:26:54 PM UTC-5, William wrote:
>
>
> On Mon, Jul 24, 2017 at 4:18 PM Travis Scrimshaw > wrote:
>
>> Yes, you can. You should create a ticket (possibly more if it makes sense
>> to break it into smaller chucks) and push your code there as you work on it
>> so peopl
On Mon, Jul 24, 2017 at 4:18 PM Travis Scrimshaw wrote:
> Yes, you can. You should create a ticket (possibly more if it makes sense
> to break it into smaller chucks) and push your code there as you work on it
> so people can look at it.
>
> Someone will likely suggest that you should develop it
Yes, you can. You should create a ticket (possibly more if it makes sense
to break it into smaller chucks) and push your code there as you work on it
so people can look at it.
Someone will likely suggest that you should develop it as a separate
package built on-top of Sage. However, I only see
