> On Jan 4, 2016, at 7:06 PM, Trent Nelson <tr...@snakebite.org> wrote: > > Hey Brett, all, > > I’m playing a bit of catch-up with e-mail, but it occurred to me some of the > work I did getting PyParallel switched over to github could be of benefit. > First thing that comes to mind is this wiki page where I tried to capture the > steps I used for the conversion and subsequent keeping-in-sync: > > https://github.com/pyparallel/pyparallel/wiki/Source-Control > > They’re very rough notes but may prove useful. Should *hopefully* be > repeatable. One issue I noticed after the fact is that a couple of the > renames > that happened when we went 2.x->3.x (like ConfigParser.py -> configparser.py) > didn’t get picked up by the hg->git conversion so I had to manually fix them > with commits like this: > https://github.com/pyparallel/pyparallel/commit/d3654f13048c8d6185a4c4b7953cbe8bd46b5d83 > > (I’ll be able to produce a proper list of the exact ones I had to fix… I just > wanted to get this e-mail out there for now.)
You probably did this on OS X or another case insensitive filesystem yea? I had the same problem the first time I did the CPython demo repository, until I did it on Linux instead. > > (That repo is sync’d up to around 3.5-ish (i.e. as of a few months ago)… all > the PyParallel stuff lived in separate *-px branches that originated from > 3.3.x-ish. Obviously we wouldn’t use that repo directly… or at least not > without git filtering out my PyParallel stuff.) > > I also made some changes to things like the buildinfo glue to work with git > instead of hg: > > https://github.com/pyparallel/pyparallel/blob/branches/3.3-px/diffs/PCbuild/make_buildinfo.c.patch > > I also updated the installer/msi.py to work with git but Steve’s since > overhauled all this stuff so I’m not sure how useful it will be: > > https://github.com/pyparallel/pyparallel/commit/ca64e60fd323875e2ca4af497d15d2f856f6c34d > > What timeframe are we looking at? There were some mentions of PSF funding in > later e-mails which I think this sort of work (once off but still needs high > precision) is well suited for. I’ll throw my hat into the ring if the > PSF<->Continuum want to formally book out some time. (I’m happy to help > either > way, but doing it formally at least guarantees time availability.) > > Regards, > > Trent. > > On Fri, Jan 01, 2016 at 07:24:53PM +0000, Brett Cannon wrote: >> If you want to read the reasons I chose GitHub over GitLab, see >> https://mail.python.org/pipermail/core-workflow/2016-January/000345.html . >> If you want to discuss the decision or help with the transition, please >> subscribe to the core-workflow mailing list. >> >> Happy 2016 everyone, and here is to hoping we will have an easier developer >> workflow by the end of this year! > >> _______________________________________________ >> python-committers mailing list >> python-committers@python.org >> https://mail.python.org/mailman/listinfo/python-committers > > _______________________________________________ > python-committers mailing list > python-committers@python.org > https://mail.python.org/mailman/listinfo/python-committers ----------------- Donald Stufft PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers
