Re: [Python-Dev] release cadence

2016-07-08 Thread Matthias Klose
On 05.07.2016 21:11, Brett Cannon wrote:
> On Tue, 5 Jul 2016 at 10:45 Barry Warsaw  wrote:
> 
>> On Jul 04, 2016, at 10:31 AM, Nick Coghlan wrote:
>>
>>> While we liked the "consistent calendar cadence that is some multiple
>>> of 6 months" idea, several of us thought 12 months was way too short
>>> as it makes for too many entries in third party support matrices.
>>
>> 18 months for a major release cadence still seems right to me.  Downstreams
>> and third-parties often have to go through *a lot* of work to ensure
>> compatibility, and try as we might, every Python release breaks
>> *something*.
>> Major version releases trigger a huge cascade of other work for lots of
>> other
>> people, and I don't think shortening that would be for the overall
>> community
>> good.  It just feels like we'd always be playing catch up.
>>
> 
> Sticking w/ 18 months is also fine, but then I would like to discuss
> choosing what months we try to release to get into a date-based release
> cadence so we know that every e.g. December and June are when releases
> typically happen thanks to our 6 month bug-fix release cadence. This has
> the nice benefit of all of us being generally aware of when a bug-fix
> release is coming up instead of having to check the PEP or go through our
> mail archive to find out what month a bug-fix is going to get cut (and also
> something the community to basically count on).

I like the 18 months cycle, because it's a multiple of six, which fits the
Ubuntu release cadence (as as I understand, the Fedora cadence as well).
Sometimes it might be ambitious to update reverse dependencies in the distro
within two months until the distro freeze, and two more months during the freeze
leading to a distro release, but such is life, and it's then up to distro
maintainers of LTS releases to prepare the distro for a new version with only
four months left.

My hope with time based releases is that also upstreams will start testing with
new versions more early when they can anticipate the release date.

Matthias

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


[Python-Dev] digital panels processing text sowftware write with Python language

2016-07-08 Thread Hadi Montazami safavi via Python-Dev
Dear SirsWith thanks, iam looking digital panels processing text sowftware 
write with Python languagefor my project.Could you please guide me if there is 
or guiding to write it personally.Thanking you in advance and awaiting.With 
best regards.M.Safavi___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] digital panels processing text sowftware write with Python language

2016-07-08 Thread Steven D'Aprano
On Fri, Jul 08, 2016 at 01:16:00PM +, Hadi Montazami safavi via Python-Dev 
wrote:

> Dear SirsWith thanks, iam looking digital panels processing text 
> sowftware write with Python languagefor my project.Could you please 
> guide me if there is or guiding to write it personally.Thanking you in 
> advance and awaiting.With best regards.M.Safavi

Sorry, we cannot help you on this list. It is for the development of the 
Python interpreter, not for projects using Python.

Please try the Python-List mailing list, they may be able to help you.

https://mail.python.org/mailman/listinfo/python-list


-- 
Steve
___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


[Python-Dev] Summary of Python tracker Issues

2016-07-08 Thread Python tracker

ACTIVITY SUMMARY (2016-07-01 - 2016-07-08)
Python tracker at http://bugs.python.org/

To view or respond to any of the issues listed below, click on the issue.
Do NOT respond to this message.

Issues counts and deltas:
  open5550 ( +5)
  closed 33676 (+28)
  total  39226 (+33)

Open issues with patches: 2427 


Issues opened (22)
==

#23908: Check path arguments of os functions for null character
http://bugs.python.org/issue23908  reopened by koobs

#26765: Factor out common bytes and bytearray implementation
http://bugs.python.org/issue26765  reopened by serhiy.storchaka

#27441: redundant assignments to ob_size of new ints that _PyLong_New 
http://bugs.python.org/issue27441  opened by Oren Milman

#27442: expose the Android API level in sysconfig.get_config_vars()
http://bugs.python.org/issue27442  opened by xdegaye

#27444: Python doesn't build due to test_float.py broken on non-IEEE m
http://bugs.python.org/issue27444  opened by stark

#27445: Charset instance not passed to set_payload()
http://bugs.python.org/issue27445  opened by claudep

#27446: struct: allow per-item byte order
http://bugs.python.org/issue27446  opened by zwol

#27447: python -m doctest script_file_with_no_py_extension produces co
http://bugs.python.org/issue27447  opened by towb

#27448: Race condition in subprocess.Popen which causes a huge memory 
http://bugs.python.org/issue27448  opened by aonishuk

#27450: bz2: BZ2File should expose compression level as an attribute
http://bugs.python.org/issue27450  opened by joshtriplett

#27451: gzip.py: Please save more of the gzip header for later examina
http://bugs.python.org/issue27451  opened by joshtriplett

#27452: IDLE: Cleanup config code
http://bugs.python.org/issue27452  opened by terry.reedy

#27453: $CPP invocation in configure must use $CPPFLAGS
http://bugs.python.org/issue27453  opened by Chi Hsuan Yen

#27454: PyUnicode_InternInPlace can use PyDict_SetDefault
http://bugs.python.org/issue27454  opened by methane

#27455: Fix tkinter examples to be PEP8 compliant
http://bugs.python.org/issue27455  opened by John Hagen

#27456: TCP_NODELAY
http://bugs.python.org/issue27456  opened by j1m

#27461: Optimize PNGs
http://bugs.python.org/issue27461  opened by scop

#27464: Document that SplitResult & friends are namedtuples
http://bugs.python.org/issue27464  opened by kmike

#27465: IDLE:Make help source menu entries unique and sorted.
http://bugs.python.org/issue27465  opened by terry.reedy

#27466: [Copy from github user macartur] time2netscape missing comma
http://bugs.python.org/issue27466  opened by Robby Daigle

#27468: Erroneous memory behaviour for objects created in another thre
http://bugs.python.org/issue27468  opened by Adria Garriga

#27469: Unicode filename gets crippled on Windows when drag and drop
http://bugs.python.org/issue27469  opened by Drekin



Most recent 15 issues with no replies (15)
==

#27469: Unicode filename gets crippled on Windows when drag and drop
http://bugs.python.org/issue27469

#27468: Erroneous memory behaviour for objects created in another thre
http://bugs.python.org/issue27468

#27464: Document that SplitResult & friends are namedtuples
http://bugs.python.org/issue27464

#27451: gzip.py: Please save more of the gzip header for later examina
http://bugs.python.org/issue27451

#27446: struct: allow per-item byte order
http://bugs.python.org/issue27446

#27445: Charset instance not passed to set_payload()
http://bugs.python.org/issue27445

#27435: ctypes and AIX - also for 2.7.X (and later)
http://bugs.python.org/issue27435

#27428: Document WindowsRegistryFinder inherits from MetaPathFinder
http://bugs.python.org/issue27428

#27427: Add new math module tests
http://bugs.python.org/issue27427

#27426: Encoding mismatch causes some tests to fail on Windows
http://bugs.python.org/issue27426

#27420: Docs for os.link - say what happens if link already exists
http://bugs.python.org/issue27420

#27411: Possible different behaviour of explicit and implicit __dict__
http://bugs.python.org/issue27411

#27409: List socket.SO_*, SCM_*, MSG_*, IPPROTO_* symbols
http://bugs.python.org/issue27409

#27408: Document importlib.abc.ExecutionLoader implements get_data()
http://bugs.python.org/issue27408

#27404: Misc/NEWS: add [Security] prefix to Python 3.5.2 changelog
http://bugs.python.org/issue27404



Most recent 15 issues waiting for review (15)
=

#27466: [Copy from github user macartur] time2netscape missing comma
http://bugs.python.org/issue27466

#27461: Optimize PNGs
http://bugs.python.org/issue27461

#27455: Fix tkinter examples to be PEP8 compliant
http://bugs.python.org/issue27455

#27454: PyUnicode_InternInPlace can use PyDict_SetDefault
http://bugs.python.org/issue27454

#27453: $CPP invocation in configure must use $CPPFLAGS
http://bugs.python.org/issue27453

#27452: IDLE: Cleanup config code
http://bugs.python.org/issue27452

#27448: Race

[Python-Dev] Reminder: 3.6.0a3 shapshot 2016-07-11 12:00 UTC

2016-07-08 Thread Ned Deily
The next alpha snapshot for the 3.6 release cycle is coming up in a couple of 
days.  This is the third of four alphas we have planned.  Keep that feature 
code coming in!

As a reminder, alpha releases are intended to make it easier for the wider 
community to test the current state of new features and bug fixes for an 
upcoming Python release as a whole and for us to test the release process.  
During the alpha phase, features may be added, modified, or deleted up until 
the start of the beta phase.  Alpha users beware!

Looking ahead, the last alpha release, 3.6.0a4, will follow next month on 
2016-08-15.  This is a slight change from the previous schedule.  Due to 
popular request, we're moved the feature code cutoff date, 3.6.0b1, from 
Wednesday, 09-07, to Monday, 09-12, to allow a bit more time after the 
end-of-summer holiday.  In doing so, it seems to make sense to move the final 
alpha back a week to give a bit more time there for check-ins.

To recap:

2016-07-11 ~12:00 UTC: code snapshot for 3.6.0 alpha 3

2016-08-15 ~12:00 UTC: code snapshot for 3.6.0 alpha 4. (**CHANGED**, was 08-08)

now to 2016-09-12: Alpha phase (unrestricted feature development)

2016-09-12: 3.6.0 feature code freeze, 3.7.0 feature development begins 
(**CHANGED**, was 09-07)

2016-09-12 to 2016-12-04: 3.6.0 beta phase (bug and regression fixes, no new 
features)

2016-12-04 3.6.0 release candidate 1 (3.6.0 code freeze)

2016-12-16 3.6.0 release (3.6.0rc1 plus, if necessary, any dire emergency fixes)

--Ned


https://www.python.org/dev/peps/pep-0494/

--
  Ned Deily
  [email protected] -- []

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