[SciPy-Dev] Status of Migrating Issues to Github?

Thouis (Ray) Jones thouis@gmail....
Mon Feb 18 12:53:36 CST 2013

On Mon, Feb 18, 2013 at 1:28 PM, Skipper Seabold <jsseabold@gmail.com> wrote:
> On Mon, Feb 18, 2013 at 1:19 PM, Pauli Virtanen <pav@iki.fi> wrote:
>> Hi,
>> 18.02.2013 20:02, Skipper Seabold kirjoitti:
>> > Just curious what the status of migrating the issues to github for scipy
>> > is? I think this was on the table right?
>> It's on the table, but AFAIK nobody is actively working on it.
>> Though, I'm still kind of wondering a bit how I'd do bugreports such as
>> this: http://projects.scipy.org/scipy/ticket/1840
>> The data file is an integral part of the report, and cannot easily be
>> factored out. If I put it in Dropbox or some random place like that, it
>> won't stay there necessarily for long...
> It's a hack, but since the trac links are persistent, we could make the Trac read-only or something and insert issue attachments as links into the github issues. I haven't looked at the migration scripts how easy it would be to do this.
> Trac Attachment (2/06/13): [Test data file](http://projects.scipy.org/scipy/attachment/ticket/1840/estimate_gradients_hang.npy)

That's what we did for the numpy trac->github migration.  All the
attachments from Trac still live there.

An example: https://github.com/numpy/numpy/issues/2490


More information about the SciPy-Dev mailing list