Re: Merecurial and Python-2.7.x, Python-3.Y

2016-10-02 Thread Michael Felt
On 02/10/2016 19:01, Ned Batchelder wrote: On Saturday, October 1, 2016 at 9:25:57 PM UTC-4, Michael Felt wrote: Finally, I got to where I understood what needed to be done to get both Mercurial built - and the the new SSL requirements met. So, running: # hg clone https://hg.python.org/cpyth

Re: Merecurial and Python-2.7.x, Python-3.Y

2016-10-02 Thread Ned Batchelder
On Saturday, October 1, 2016 at 9:25:57 PM UTC-4, Michael Felt wrote: > Finally, I got to where I understood what needed to be done to get both > Mercurial built - and the the new SSL requirements met. > > So, running: > > # hg clone https://hg.python.org/cpython > > works. What is the next ste

Re: Merecurial and Python-2.7.x, Python-3.Y

2016-10-02 Thread Michael Felt
On 02/10/2016 08:34, Terry Reedy wrote: No. By default, the working directory for a clone is for the default branch. Any clone can be 'updated' to any branch. I have each share clone updated to a different branch, so I never update to a different branch. -- This answers my underlying questi

Re: Merecurial and Python-2.7.x, Python-3.Y

2016-10-01 Thread Terry Reedy
On 10/1/2016 5:31 AM, Michael Felt wrote: Finally, I got to where I understood what needed to be done to get both Mercurial built - and the the new SSL requirements met. So, running: # hg clone https://hg.python.org/cpython works. What is the next step to getting Python-2.7 AND Python-3.7 so I