[python-committers] Re: getting old branches/releases

[Ned Deily]

On Feb 11, 2020, at 19:26, Ethan Furman  wrote:
> On 02/11/2020 04:04 PM, Mariatta wrote:
>> On Tue, Feb 11, 2020 at 3:49 PM Ethan Furman wrote:
> 
>>> I'm trying to get the 3.3 and 3.4 branches so I can check my libraries' 
>>> compatibility with older versions, but I do not see those branches as being 
>>> available:
>>> How can I get those?
>> 3.3 and 3.4 existed before the migration from GitHub, so we don't have the 
>> branches.
>> They are in the repo as git tags.
>> Try:
>> # list all git tags matching v.3.3
>> git tag -l 'v3.3*'
>> # checkout the v.3.3.0 tag to a local branch
>> git checkout tags/v.3.3.0 -b my-own-3.3.0-branch
> 
> Nice!  Many thanks!

It's a bit simpler than that.  You don't need to specify `tags/` when 
referencing tags.

git checkout v3.3.7   # for final 3.3 release (in detached HEAD mode)

git checkout v3.3.7 -b v3.3.7 # to also create a local branch

git checkout 3.3 -b 3.3   # for the final state of the 3.3 branch


https://git-scm.com/book/en/v2/Git-Basics-Tagging

--
  Ned Deily
  n...@python.org -- []
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/SJJ6JQNNK3ARPUWYF45POSTIR5OJH7TI/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: getting old branches/releases

[Martin Panter]

>> I'm trying to get the 3.3 and 3.4 branches so I can check my libraries 
>> compatibility with older versions, but I do not see those branches as being 
>> available:
>>
>> How can I get those?
>>
>>
>
>
> 3.3 and 3.4 existed before the migration from GitHub, so we don't have the 
> branches.
>
> They are in the repo as git tags.
>
> Try:
>
> # list all git tags matching v.3.3
> git tag -l 'v3.3*'
>
> # checkout the v.3.3.0 tag to a local branch
> git checkout tags/v.3.3.0 -b my-own-3.3.0-branch

I remember a few years ago the older Git branches were changed to
tags, to get rid of them from Git Hub's list of branches I think.
Maybe these tags are what you are after (note there is no v prefix):

$ git ls-remote git://github.com/python/cpython
[thousands of PR branches etc skipped]
4dea2538537ba8ef14e4296217abcd7a45cb25cerefs/tags/3.3
bf9cccb2b54ad2c641ea78435a8618a6d251491erefs/tags/3.3^{}
6bedc750c2d3ca75671c3a6b261592455e0f5850refs/tags/3.4
05c28b08f6e2fc8782472b026c98a3fdd61a2ba9refs/tags/3.4^{}
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/RAHJKSEJT4B5VVLNCOMYHZFB574XTAUS/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: getting old branches/releases

[Mariatta]

Great! Perhaps we should have this info in devguide.
https://github.com/python/devguide/issues/572
Welcoming PR.
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/IPRJVG2USHVP4QUK4RZKJK4UMNTZRKQN/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: getting old branches/releases

[Ethan Furman]

On 02/11/2020 04:04 PM, Mariatta wrote:

On Tue, Feb 11, 2020 at 3:49 PM Ethan Furman wrote:



I'm trying to get the 3.3 and 3.4 branches so I can check my libraries' 
compatibility with older versions, but I do not see those branches as being 
available:

How can I get those?


3.3 and 3.4 existed before the migration from GitHub, so we don't have the 
branches.

They are in the repo as git tags.

Try:

# list all git tags matching v.3.3
git tag -l 'v3.3*'

# checkout the v.3.3.0 tag to a local branch
git checkout tags/v.3.3.0 -b my-own-3.3.0-branch


Nice!  Many thanks!

--
~Ethan~
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/74EFB7W6AVOPSE2DMNNJ2ZZEIZ5G2RS5/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: getting old branches/releases

[Mariatta]

On Tue, Feb 11, 2020 at 3:49 PM Ethan Furman  wrote:

>
> I'm trying to get the 3.3 and 3.4 branches so I can check my libraries
> compatibility with older versions, but I do not see those branches as being
> available:
>
> How can I get those?
>
>
>

3.3 and 3.4 existed before the migration from GitHub, so we don't have the
branches.

They are in the repo as git tags.

Try:

# list all git tags matching v.3.3
git tag -l 'v3.3*'

# checkout the v.3.3.0 tag to a local branch
git checkout tags/v.3.3.0 -b my-own-3.3.0-branch
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/6TF7LBUDYGDCSU3QA5PLGARATIYQYUY3/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] getting old branches/releases

[Ethan Furman]

Howdy!

I'm trying to get the 3.3 and 3.4 branches so I can check my libraries 
compatibility with older versions, but I do not see those branches as being 
available:

$ git branch --remote 89
  remotes/upstream/2.7
  remotes/upstream/3.5
  remotes/upstream/3.6
  remotes/upstream/3.7
  remotes/upstream/3.8
  remotes/upstream/buildbot-custom
  remotes/upstream/master

How can I get those?

--
~Ethan~
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/64M6FJAWLQ7LGLUQTXOOPIKQCKT2AN5G/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: A urlparse regression in minor version

[Łukasz Langa]

I'll let others voice their opinions but my intuition for 3.8.x is to leave 
your patch be. True, it should not have been backported but it was, and it was 
already released as part of 3.8.1 and now 3.8.2rc1.

The user will have to special-case the change in behavior anyway. I feel like 
it is easier for them to do so by only special-casing "sys.version_info < (3, 
8, 1)". The alternative if you revert your patch will be to special case both 
"sys.version_info < (3, 9)" and "sys.version_info == (3, 8, 1)" (let alone 
3.8.2rc1). That is worse I think.

So, the only thing to do is to clearly document that there was a change, not in 
3.9 but in 3.8.1 and forward.

Agreed that it's a bit of a mess for 3.7 since that was way later in the 
release cadence with only 3.7.6 getting the change. I will let Ned decide here.

- Ł


> On 10 Feb 2020, at 15:27, Senthil Kumaran  wrote:
> 
> Hello Python-Committers,
> 
> In https://bugs.python.org/issue27657 , I 
> introduced a regression in a minor release.
> The original patch to parsing logic of URL, cleaned up a lot of corner cases 
> (https://github.com/python/cpython/pull/661 
> ) and I felt good about the 
> change.
> However, the mistake was with the backport.
> 
> Demo:
> 
> $ ./python 
> Python 3.8.0 (default, Feb 10 2020, 06:15:43) 
> [GCC 9.2.1 20191008] on linux
> Type "help", "copyright", "credits" or "license" for more information.
> >>> from urllib.parse import urlparse
> >>> urlparse('localhost:8080')
> ParseResult(scheme='', netloc='', path='localhost:8080', params='', query='', 
> fragment='')
> 
> 
> 
> $ ./python 
> Python 3.8.1+ (heads/3.8:b086ea5edc, Feb 10 2020, 06:15:44) 
> [GCC 9.2.1 20191008] on linux
> Type "help", "copyright", "credits" or "license" for more information.
> >>> from urllib.parse import urlparse
> >>> urlparse('localhost:8080')
> ParseResult(scheme='localhost', netloc='', path='8080', params='', query='', 
> fragment='')
> 
> ---
> 
> When I read an associated bug report against a user of the software (like 
> this: https://github.com/mozilla/bleach/issues/503 
> ) - I feel that this was a 
> mistake.
> The change of test-suite in minor versions should have alerted me, but I seem 
> to have missed it.
> 
> I am planning to revert this change in 3.8.2 and 3.7.7
> Should I highlight this in any documentation?  Thoughts and opinions?
> 
> Thank you,
> Senthil
> 
> 
> ___
> python-committers mailing list -- python-committers@python.org
> To unsubscribe send an email to python-committers-le...@python.org
> https://mail.python.org/mailman3/lists/python-committers.python.org/
> Message archived at 
> https://mail.python.org/archives/list/python-committers@python.org/message/2ONL562L35S77FGCLYH2ZDWVAXHH2BZP/
> Code of Conduct: https://www.python.org/psf/codeofconduct/

___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/AEXBKUEPJP7ZHAXYDZNVIUB5G2MOHFDS/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: A urlparse regression in minor version

[Senthil Kumaran]

Hi Łukasz ,

I wanted to push a revert in urlparse module in Python 3.8.2

I sent a note about this to python-committers, are you okay with this?

Thanks,
Senthil

On Mon, Feb 10, 2020 at 6:27 AM Senthil Kumaran  wrote:

> Hello Python-Committers,
>
> In https://bugs.python.org/issue27657, I introduced a regression in a
> minor release.
> The original patch to parsing logic of URL, cleaned up a lot of corner
> cases (https://github.com/python/cpython/pull/661) and I felt good about
> the change.
> However, the mistake was with the backport.
>
> Demo:
>
> $ ./python
> Python 3.8.0 (default, Feb 10 2020, 06:15:43)
> [GCC 9.2.1 20191008] on linux
> Type "help", "copyright", "credits" or "license" for more information.
> >>> from urllib.parse import urlparse
> >>> urlparse('localhost:8080')
> ParseResult(scheme='', netloc='', path='localhost:8080', params='',
> query='', fragment='')
>
> 
>
> $ ./python
> Python 3.8.1+ (heads/3.8:b086ea5edc, Feb 10 2020, 06:15:44)
> [GCC 9.2.1 20191008] on linux
> Type "help", "copyright", "credits" or "license" for more information.
> >>> from urllib.parse import urlparse
> >>> urlparse('localhost:8080')
> ParseResult(scheme='localhost', netloc='', path='8080', params='',
> query='', fragment='')
>
> ---
>
> When I read an associated bug report against a user of the software (like
> this: https://github.com/mozilla/bleach/issues/503) - I feel that this
> was a mistake.
> The change of test-suite in minor versions should have alerted me, but I
> seem to have missed it.
>
> I am planning to revert this change in 3.8.2 and 3.7.7
> Should I highlight this in any documentation?  Thoughts and opinions?
>
> Thank you,
> Senthil
>
>
>
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/MMYBXVO5B3EIBAM2KMKZKNPPX4Z7ZC2L/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] [RELEASE] Python 3.8.2rc1 is now available for testing

[Łukasz Langa]

Python 3.8.2rc1 is the release candidate of the second maintenance release of 
Python 3.8. Go get it here:

https://www.python.org/downloads/release/python-382rc1/ 


Assuming no critical problems are found prior to 2020-02-17, the scheduled 
release date for 3.8.2 (as well as 3.9.0 alpha 4!), no code changes are planned 
between this release candidate and the final release.
That being said, please keep in mind that this is a pre-release of 3.8.2 and as 
such its main purpose is testing.

Maintenance releases for the 3.8 series will continue at regular bi-monthly 
intervals, with 3.8.3 planned for April 2020 (during sprints at PyCon US).

What’s new?

The Python 3.8 series is the newest feature release of the Python language, and 
it contains many new features and optimizations. See the “What’s New in Python 
3.8 ” document for more 
information about features included in the 3.8 series.

Detailed information about all changes made in version 3.8.2 specifically can 
be found in its change log 
.

We hope you enjoy Python 3.8!

Thanks to all of the many volunteers who help make Python Development and these 
releases possible! Please consider supporting our efforts by volunteering 
yourself or through organization contributions to the Python Software 
Foundation.

https://www.python.org/psf/ 


- Ł
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/TNYC4DPNMKAGRERBFEXTJ4RE4CRB7WW3/
Code of Conduct: https://www.python.org/psf/codeofconduct/