Google already got back to me -- they can repro my problem and will try to fix it.
On Wed, Apr 8, 2015 at 12:11 PM, Yury Selivanov <[email protected]> wrote: > Yes, I can’t find anything particular about 208 (for instance) to see why > it wasn’t exported. > > BTW, there is another project to migrate issues: > https://github.com/arthur-debert/google-code-issues-migrator > > Yury > > > On Apr 8, 2015, at 3:04 PM, Guido van Rossum <[email protected]> wrote: > > > > The Google code migration tool claims to migrate issues. You can see how > far it got in this example repo:: https://github.com/gvanrossum/tulip-try1 > -- apparently the issue migration is flaky. :-( > > > > But I won't declare the package migrated until the issues and wiki have > been migrated fully. > > > > On Wed, Apr 8, 2015 at 12:00 PM, Yury Selivanov <[email protected]> > wrote: > > Hi Guido, > > > > How will we migrate issues? Just recreate them on guthub, or abandon and > start from scratch? > > > > I was going to continue discussion on > https://code.google.com/p/tulip/issues/detail?id=208 > > > > Yury > > > > > > On Wednesday, April 8, 2015 at 1:32:40 PM UTC-4, Guido van Rossum wrote: > > Because Google code is shutting down, I'm about to migrate the Tulip > repo to GitHub. I'll post here again once the migration is done. > > > > -- > > --Guido van Rossum (python.org/~guido) > > > > > > > > -- > > --Guido van Rossum (python.org/~guido) > > -- --Guido van Rossum (python.org/~guido)
