We retagged Python 3.5.0rc1 today to fix two bugs that popped up late in
the process. Release candidates are supposed to be software you
genuinely would release, and I couldn't release Python with both those
bugs. This delay rippled through the whole process, so it just isn't
going out ton
As of Python 3.5.0rc1, the canonical repository for Python 3.5.0 is
*no longer* on hg.python.org. Instead, it's hosted on Bitbucket on
my personal account, here:
https://bitbucket.org/larry/cpython350
Since 3.5.0rc1 isn't out yet I'm keeping the repository private for now.
Once 3.5.0 rc1 i
We have all been there: you fix something in some maintenance branch, do
your `hg pull` into the default branch, and everything *but* Misc/NEWS
merges cleanly. You typically revert Misc/NEWS, commit your forward-ported
change to default, and then move on with your life. It would be much easier
if M
A quick hg tip for making sure you check out the right branch: end the URL
on #3.5 and it will start the repo out with the 3.5 as the active branch.
On Mon, Aug 10, 2015, 01:28 Larry Hastings wrote:
>
> As of Python 3.5.0rc1, the canonical repository for Python 3.5.0 is
> *no longer* on hg.pytho
On behalf of the Python development community and the Python 3.5 release
team, I'm relieved to announce the availability of Python 3.5.0rc1, also
known as Python 3.5.0 Release Candidate 1.
Python 3.5 has now entered "feature freeze". By default new features
may no longer be added to Python
On 08/10/2015 01:27 AM, Larry Hastings wrote:
As of Python 3.5.0rc1, the canonical repository for Python 3.5.0 is
*no longer* on hg.python.org. Instead, it's hosted on Bitbucket on
my personal account, here:
https://bitbucket.org/larry/cpython350
Since 3.5.0rc1 isn't out yet I'm keeping
I built the source tarballs with a slightly-out-of-date tree. We
slipped the release by a day to get two fixes in, but the tree I built
from didn't have those two fixes.
I yanked the tarballs off the release page as soon as I suspected
something. I'm rebuilding the tarballs and the docs n
On 08/10/2015 05:55 PM, Larry Hastings wrote:
I yanked the tarballs off the release page as soon as I suspected
something. I'm rebuilding the tarballs and the docs now. If you
grabbed the tarball as soon as it appeared, it's slightly out of date,
please re-grab.
p.s. I should have mentioned
On 11 August 2015 at 10:38, Brett Cannon wrote:
> We have all been there: you fix something in some maintenance branch, do
> your `hg pull` into the default branch, and everything but Misc/NEWS merges
> cleanly. You typically revert Misc/NEWS, commit your forward-ported change
> to default, and th
