Re: [sage-devel] doubt in checking out and pushing to an existing ticket using plain git

2020-02-27 Thread Saket Bhatt
thanks! On Friday, February 28, 2020 at 5:34:03 AM UTC+5:30, Dima Pasechnik wrote: > > On Thu, Feb 27, 2020 at 6:35 PM Saket Bhatt > wrote: > > > > Hi! > > I am a newbie here.I am working on a ticket which do not have any branch > attached to it, I am using plain git. I want to push my change

Re: [sage-devel] How to deal with cross-references to Sphinx documentation of other projects

2020-02-27 Thread Kwankyu Lee
On Friday, February 28, 2020 at 3:37:52 AM UTC+9, Markus Wageringel wrote: > > This is an interesting suggestion. How would this work with > non-interactive builds like on the patchbots or in CI? > So add a docbuild option `--yes-download` to prevent asking. And `--no-download` might be usefu

Re: [sage-devel] doubt in checking out and pushing to an existing ticket using plain git

2020-02-27 Thread Dima Pasechnik
On Thu, Feb 27, 2020 at 6:35 PM Saket Bhatt wrote: > > Hi! > I am a newbie here.I am working on a ticket which do not have any branch > attached to it, I am using plain git. I want to push my changes using "git > push --set-upstream trac HEAD:u/user/description" however I don't know how to > sp

[sage-devel] doubt in checking out and pushing to an existing ticket using plain git

2020-02-27 Thread Saket Bhatt
Hi! I am a newbie here.I am working on a ticket which do not have any branch attached to it, I am using plain git. I want to push my changes using "git push --set-upstream trac HEAD:u/user/description" however I don't know how to specify/attach the ticket no which u can do using git-trac comman

Re: [sage-devel] How to deal with cross-references to Sphinx documentation of other projects

2020-02-27 Thread Michael Orlitzky
On 2/27/20 1:39 PM, Markus Wageringel wrote: > Yes, the objects.inv files are generated by Sphinx. This is the approach that > Sage currently follows with pplpy. The documentation is compiled and > installed by the spkg-postinst of pplpy. > > Applying this approach to other packages however is n

Re: [sage-devel] How to deal with cross-references to Sphinx documentation of other projects

2020-02-27 Thread Markus Wageringel
Yes, the objects.inv files are generated by Sphinx. This is the approach that Sage currently follows with pplpy. The documentation is compiled and installed by the spkg-postinst of pplpy. Applying this approach to other packages however is not easily doable. When building the numpy documentatio

Re: [sage-devel] How to deal with cross-references to Sphinx documentation of other projects

2020-02-27 Thread Markus Wageringel
This is an interesting suggestion. How would this work with non-interactive builds like on the patchbots or in CI? Would the user be asked right before downloading, i.e. during the docbuild phase, or perhaps when running configure, so it can fail early? > Am 27.02.2020 um 03:30 schrieb Kwankyu