Re: [Python-Dev] Python 2.7.13 release dates

[Benjamin Peterson]

Okay, now that we're heard from the other side, and I lacking a concrete
reason to delay the release, I'm putting 2.7.13 back at the original
dates.

On Tue, Nov 29, 2016, at 06:34, Matthias Klose wrote:
> same here.
> https://wiki.debian.org/DebianStretch shows the final Debian release
> freeze for
> 2016-02-05, which would be a bit close for a 2.7.13 release.
> 
> On 29.11.2016 15:12, Steve Dower wrote:
> > I would much rather keep it in December, as I've already made scheduling 
> > decisions around the planned release date and there are fixes in 2.7.13 
> > that I was expecting to be available by the end of the year. One month is 
> > highly impactful for me.
> > 
> > Is this schedule change going to remove the month from 2.7.14? Or are we 
> > slipping all the rest of the releases (apart from the very last one at the 
> > end of 2019, presumably)? I too would like to know the intended use of the 
> > extra time.
> > 
> > Top-posted from my Windows Phone
> > 
> > -Original Message-
> > From: "Benjamin Peterson" 
> > Sent: ‎11/‎29/‎2016 0:04
> > To: "Raymond Hettinger" ; "Serhiy Storchaka" 
> > 
> > Cc: "Python-Dev@Python. Org" 
> > Subject: Re: [Python-Dev] Python 2.7.13 release dates
> > 
> > Okay, by popular demand, 2.7.13 now happens in January.
> > 
> > I'm curious what people are planning to do to 2.7 with the extra 5
> > weeks. The 2.7 branch is a place to put occasional conservative bug
> > fixes, which we aggregate and release every 6 months. It shouldn't
> > really need special attention or become less stable depending on the
> > release stage of Python 3.
> > 
> > On Mon, Nov 28, 2016, at 20:50, Raymond Hettinger wrote:
> >>
> >>> On Nov 28, 2016, at 10:36 AM, Serhiy Storchaka  
> >>> wrote:
> >>>
> >>> On 28.11.16 09:06, Benjamin Peterson wrote:
>  I've have just updated PEP 373 to say that Python 2.7.13 release
>  candidate 1 will be released on December 3. The final will follow two
>  weeks later on December 17. If there are delays in the process, the
>  final will likely to pushed into January.
> >>>
> >>> Could it be delayed until 3.6.0 released? I paused fixing non-critical 
> >>> and non-documentation bugs while 3.6 in pre-release stage and this could 
> >>> include bugs that affect 2.7.
> >>>
> >>> In additional, we always receive increased number of bug reports in the 
> >>> first one or two weeks after releasing new Python version. Some of these 
> >>> reports are about regressions introduced by bugfixes. If delay bugfix 
> >>> releases after new version release, we could fix regressions caused by 
> >>> backported bugfixes and make bugfix releases more reliable.
> >>
> >> +1 on delaying 2.7.13 for a bit.  As long as it doesn't muck up
> >> Benjamin's schedule, the extra time would be helpful (Python 3.6.0 got
> >> all the focus recently).
> >>
> >>
> >> Raymond
> >> ___
> >> Python-Dev mailing list
> >> Python-Dev@python.org
> >> https://mail.python.org/mailman/listinfo/python-dev
> >> Unsubscribe:
> >> https://mail.python.org/mailman/options/python-dev/benjamin%40python.org
> > ___
> > Python-Dev mailing list
> > Python-Dev@python.org
> > https://mail.python.org/mailman/listinfo/python-dev
> > Unsubscribe: 
> > https://mail.python.org/mailman/options/python-dev/steve.dower%40python.org
> > 
> > 
> > 
> > ___
> > Python-Dev mailing list
> > Python-Dev@python.org
> > https://mail.python.org/mailman/listinfo/python-dev
> > Unsubscribe: 
> > https://mail.python.org/mailman/options/python-dev/doko%40ubuntu.com
> > 
> 
> ___
> Python-Dev mailing list
> Python-Dev@python.org
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe:
> https://mail.python.org/mailman/options/python-dev/benjamin%40python.org
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] Python private and protected variables and methods

[Terry Reedy]

On 11/29/2016 9:39 AM, Annapoornima Koppad wrote:


While teaching Python protected variables, I figured out the oddity
about Python.
I am using Python 2.7.12+ for my teaching.
There is not really a concept of protected variables in Python, is it?


Only the _ convention.


For a more detailed explanation of what I am trying to do, please read
this article,
http://radek.io/2011/07/21/private-protected-and-public-in-python/

It that is the case, Python is not suitable for companies that require
secure transactions such as  Banking softwares. What solution are
possible to overcome data masquerading attempts that might result
because of this?


Hello, Annapoornima

pydev list is for development of future Python and Cpython.  Questions 
about using current Python should be directed to python-list or other 
forums such as Stackoverflow or specialized lists.


I know that Python is heavily used in the American finacial sector but 
not anything about specific security practices.  I expect python-list to 
have readers that do know something.  When you post, try to be a bit 
more specific about particular threat models.


--
Terry Jan Reedy

___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

[Python-Dev] Python private and protected variables and methods

[Annapoornima Koppad]

Dear All,

While teaching Python protected variables, I figured out the oddity about
Python.

I am using Python 2.7.12+ for my teaching.

There is not really a concept of protected variables in Python, is it?

For a more detailed explanation of what I am trying to do, please read this
article, http://radek.io/2011/07/21/private-protected-and-public-in-python/

It that is the case, Python is not suitable for companies that require
secure transactions such as  Banking softwares. What solution are possible
to overcome data masquerading attempts that might result because of this?

Thanks and regards,
Annapoornima
www.pyladies.co.in
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] Python 2.7.13 release dates

[Matthias Klose]

same here.
https://wiki.debian.org/DebianStretch shows the final Debian release freeze for
2016-02-05, which would be a bit close for a 2.7.13 release.

On 29.11.2016 15:12, Steve Dower wrote:
> I would much rather keep it in December, as I've already made scheduling 
> decisions around the planned release date and there are fixes in 2.7.13 that 
> I was expecting to be available by the end of the year. One month is highly 
> impactful for me.
> 
> Is this schedule change going to remove the month from 2.7.14? Or are we 
> slipping all the rest of the releases (apart from the very last one at the 
> end of 2019, presumably)? I too would like to know the intended use of the 
> extra time.
> 
> Top-posted from my Windows Phone
> 
> -Original Message-
> From: "Benjamin Peterson" 
> Sent: ‎11/‎29/‎2016 0:04
> To: "Raymond Hettinger" ; "Serhiy Storchaka" 
> 
> Cc: "Python-Dev@Python. Org" 
> Subject: Re: [Python-Dev] Python 2.7.13 release dates
> 
> Okay, by popular demand, 2.7.13 now happens in January.
> 
> I'm curious what people are planning to do to 2.7 with the extra 5
> weeks. The 2.7 branch is a place to put occasional conservative bug
> fixes, which we aggregate and release every 6 months. It shouldn't
> really need special attention or become less stable depending on the
> release stage of Python 3.
> 
> On Mon, Nov 28, 2016, at 20:50, Raymond Hettinger wrote:
>>
>>> On Nov 28, 2016, at 10:36 AM, Serhiy Storchaka  wrote:
>>>
>>> On 28.11.16 09:06, Benjamin Peterson wrote:
 I've have just updated PEP 373 to say that Python 2.7.13 release
 candidate 1 will be released on December 3. The final will follow two
 weeks later on December 17. If there are delays in the process, the
 final will likely to pushed into January.
>>>
>>> Could it be delayed until 3.6.0 released? I paused fixing non-critical and 
>>> non-documentation bugs while 3.6 in pre-release stage and this could 
>>> include bugs that affect 2.7.
>>>
>>> In additional, we always receive increased number of bug reports in the 
>>> first one or two weeks after releasing new Python version. Some of these 
>>> reports are about regressions introduced by bugfixes. If delay bugfix 
>>> releases after new version release, we could fix regressions caused by 
>>> backported bugfixes and make bugfix releases more reliable.
>>
>> +1 on delaying 2.7.13 for a bit.  As long as it doesn't muck up
>> Benjamin's schedule, the extra time would be helpful (Python 3.6.0 got
>> all the focus recently).
>>
>>
>> Raymond
>> ___
>> Python-Dev mailing list
>> Python-Dev@python.org
>> https://mail.python.org/mailman/listinfo/python-dev
>> Unsubscribe:
>> https://mail.python.org/mailman/options/python-dev/benjamin%40python.org
> ___
> Python-Dev mailing list
> Python-Dev@python.org
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe: 
> https://mail.python.org/mailman/options/python-dev/steve.dower%40python.org
> 
> 
> 
> ___
> Python-Dev mailing list
> Python-Dev@python.org
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe: 
> https://mail.python.org/mailman/options/python-dev/doko%40ubuntu.com
> 

___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] Python 2.7.13 release dates

[Matthias Klose]

On 28.11.2016 20:38, Larry Hastings wrote:
> On 11/28/2016 10:42 AM, Guido van Rossum wrote:
>> Perhaps (un)related, is the release schedule for 3.5.3 set yet? (I'm holding
>> off putting a new version of typing.py on typeshed until that's out.)
> 
> Not set in stone, but I have a rough plan.  I want the dust to settle around 
> 3.6
> first.  So, have an RC1 in January, and then the final release two weeks 
> later. 
> I'm traveling the second week of January (#DSDad) so the RC would be either
> before or after that.

https://wiki.debian.org/DebianStretch shows the final Debian release freeze for
2016-02-05, which would be a bit close for a 3.5.3 release.  So anything with
some buffer to Feb 05 would be appreciated.

___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] Tests breakage with latest openssl (issue28689)

[Christian Heimes]

On 2016-11-28 18:16, Charalampos Stratakis wrote:
> Hi Christian and thanks for the fast reply,
> 
> It's great to hear that the latest version is working fine. Do you have 
> anymore details on the fix/breakage?
> 
> The latest commit at Fedora's rawhide openssl package  is at [0]. Is it 
> missing something?
> 
> [0] 
> http://pkgs.fedoraproject.org/cgit/rpms/openssl.git/commit/?id=e443a79334446ac0dc14fdf7c062386f92bbc7a0

Hi Charalampos,

Sorry, I don't have more details other than the Python and OpenSSL
tickets. It sounds like the Fedora rawhide fix is not sufficient and may
lack something. I don't have any spare cycles to look at the patch.

A distribution patch doesn't work for users of other distributions, too.
Let's see if I can get the OpenSSL team to release another version soonish.

Christian

___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] Python 2.7.13 release dates

[Steve Dower]

I would much rather keep it in December, as I've already made scheduling 
decisions around the planned release date and there are fixes in 2.7.13 that I 
was expecting to be available by the end of the year. One month is highly 
impactful for me.

Is this schedule change going to remove the month from 2.7.14? Or are we 
slipping all the rest of the releases (apart from the very last one at the end 
of 2019, presumably)? I too would like to know the intended use of the extra 
time.

Top-posted from my Windows Phone

-Original Message-
From: "Benjamin Peterson" 
Sent: ‎11/‎29/‎2016 0:04
To: "Raymond Hettinger" ; "Serhiy Storchaka" 

Cc: "Python-Dev@Python. Org" 
Subject: Re: [Python-Dev] Python 2.7.13 release dates

Okay, by popular demand, 2.7.13 now happens in January.

I'm curious what people are planning to do to 2.7 with the extra 5
weeks. The 2.7 branch is a place to put occasional conservative bug
fixes, which we aggregate and release every 6 months. It shouldn't
really need special attention or become less stable depending on the
release stage of Python 3.

On Mon, Nov 28, 2016, at 20:50, Raymond Hettinger wrote:
> 
> > On Nov 28, 2016, at 10:36 AM, Serhiy Storchaka  wrote:
> > 
> > On 28.11.16 09:06, Benjamin Peterson wrote:
> >> I've have just updated PEP 373 to say that Python 2.7.13 release
> >> candidate 1 will be released on December 3. The final will follow two
> >> weeks later on December 17. If there are delays in the process, the
> >> final will likely to pushed into January.
> > 
> > Could it be delayed until 3.6.0 released? I paused fixing non-critical and 
> > non-documentation bugs while 3.6 in pre-release stage and this could 
> > include bugs that affect 2.7.
> > 
> > In additional, we always receive increased number of bug reports in the 
> > first one or two weeks after releasing new Python version. Some of these 
> > reports are about regressions introduced by bugfixes. If delay bugfix 
> > releases after new version release, we could fix regressions caused by 
> > backported bugfixes and make bugfix releases more reliable.
> 
> +1 on delaying 2.7.13 for a bit.  As long as it doesn't muck up
> Benjamin's schedule, the extra time would be helpful (Python 3.6.0 got
> all the focus recently).
> 
> 
> Raymond
> ___
> Python-Dev mailing list
> Python-Dev@python.org
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe:
> https://mail.python.org/mailman/options/python-dev/benjamin%40python.org
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/steve.dower%40python.org
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

[Python-Dev] Last call for the Call For Proposals of PythonFOSDEM 2017

[Stephane Wirtel]

Because the deadline is imminent and because we have only received some
proposals, we will extend the current deadline. The new submission deadline is
2016-12-18.

Call For Proposals
==

This is the official call for sessions for the Python devroom at FOSDEM 2017.

FOSDEM is the Free and Open source Software Developers' European Meeting, a free
and non-commercial two-day week-end that offers open source contributors a place
to meet, share ideas and collaborate.

It's the biggest event in Europe with +5000 hackers, +400 speakers.

For this edition, Python will be represented by its Community.
If you want to discuss with a lot of Python Users, it's the place to be!

Important dates
===

* Submission deadlines: 2016-12-18
* Acceptance notifications: 2016-12-23

Practical
=

* The duration for talks will be 30 minutes, including presentations and
questions and answers.
* Presentation can be recorded and streamed, sending your proposal implies
giving permission to be recorded.
* A mailing list for the Python devroom is available for discussions about
devroom organisation. You can register at this address:
https://lists.fosdem.org/listinfo/python-devroom

How to submit
=

All submissions are made in the Pentabarf event planning tool at
https://penta.fosdem.org/submission/FOSDEM17

When submitting your talk in Pentabarf, make sure to select the Python devroom
as the Track.

Of course, if you already have a user account, please reuse it.

Questions
=

Any questions, please send an email to info AT python-fosdem DOT org

Thank you for submitting your sessions and see you soon in Brussels to talk
about Python.

If you want to keep informed for this edition, you can follow our twitter
account @PythonFOSDEM.

* FOSDEM 2017: https://fosdem.org/2017
* Python Devroom: http://python-fosdem.org
* Twitter: https://twitter.com/PythonFOSDEM


Stephane

--
Stéphane Wirtel - http://wirtel.be - @matrixise
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] Python 2.7.13 release dates

[Benjamin Peterson]

Okay, by popular demand, 2.7.13 now happens in January.

I'm curious what people are planning to do to 2.7 with the extra 5
weeks. The 2.7 branch is a place to put occasional conservative bug
fixes, which we aggregate and release every 6 months. It shouldn't
really need special attention or become less stable depending on the
release stage of Python 3.

On Mon, Nov 28, 2016, at 20:50, Raymond Hettinger wrote:
> 
> > On Nov 28, 2016, at 10:36 AM, Serhiy Storchaka  wrote:
> > 
> > On 28.11.16 09:06, Benjamin Peterson wrote:
> >> I've have just updated PEP 373 to say that Python 2.7.13 release
> >> candidate 1 will be released on December 3. The final will follow two
> >> weeks later on December 17. If there are delays in the process, the
> >> final will likely to pushed into January.
> > 
> > Could it be delayed until 3.6.0 released? I paused fixing non-critical and 
> > non-documentation bugs while 3.6 in pre-release stage and this could 
> > include bugs that affect 2.7.
> > 
> > In additional, we always receive increased number of bug reports in the 
> > first one or two weeks after releasing new Python version. Some of these 
> > reports are about regressions introduced by bugfixes. If delay bugfix 
> > releases after new version release, we could fix regressions caused by 
> > backported bugfixes and make bugfix releases more reliable.
> 
> +1 on delaying 2.7.13 for a bit.  As long as it doesn't muck up
> Benjamin's schedule, the extra time would be helpful (Python 3.6.0 got
> all the focus recently).
> 
> 
> Raymond
> ___
> Python-Dev mailing list
> Python-Dev@python.org
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe:
> https://mail.python.org/mailman/options/python-dev/benjamin%40python.org
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com