[Python-Dev] Python 3.4: What to do about the Derby patches
Antoine Pitrou
solipsis at pitrou.net
Sun Feb 16 22:51:34 CET 2014
More information about the Python-Dev mailing list
Sun Feb 16 22:51:34 CET 2014
- Previous message: [Python-Dev] Python 3.4: What to do about the Derby patches
- Next message: [Python-Dev] Python 3.4: What to do about the Derby patches
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Sun, 16 Feb 2014 10:31:21 -0800 Larry Hastings <larry at hastings.org> wrote: > > Here's how I propose we move forward. > > 1) We merge the Derby patch for the builtins module into 3.4, simply > because it will "demo well". This still brings potential unstability during the rc phase, so I'd prefer this patch to wait for 3.4.1. Quoting Wikipedia: "A release candidate (RC) is a beta version with potential to be a final product, which is ready to release unless significant bugs emerge." Regards Antoine.
- Previous message: [Python-Dev] Python 3.4: What to do about the Derby patches
- Next message: [Python-Dev] Python 3.4: What to do about the Derby patches
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list