that
Steve (or someone else) would be willing to build the additional
installers for the transition period? I've done something similar on a
smaller scale with the OS X 32-bit installer for 2.7.x but that impact
is much less as the audience fo
n for some folks, others *might*
welcome the opportunity to no longer have to keep around old versions of
the tool chain, particularly if they now could use the same tool chain
to produce binaries for both Py2 and Py3.
--
Ned Deily,
n...@acm.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
pen issues. Any or all of the above costs may
apply to any changes we make. For many of our users, the best
maintenance policy for Python 2.7 would be the least change possible.
--
Ned Deily,
n...@acm.org
___
Python-Dev mailing list
Python-Dev@pyt
00
> summary:
> Closes #20872: dbm/gdbm/ndbm close methods are not documented
The 3.3 branch is open only to security fixes. Please don't backport
other patches to there.
https://docs.python.org/devguide/devcycle.html#summary
--
Ned Deily,
n...@acm.org
___
In article <53ab53a7.6050...@jcea.es>, Jesus Cea wrote:
> On 25/06/14 20:35, Ned Deily wrote:
> > The 3.3 branch is open only to security fixes. Please don't backport
> > other patches to there.
> >
> > https://docs.python.org/devguide/devcycle.html#sum
The buildbot web site seems to have been down for some hours and still
is as of 0915 UTC. I'm not sure who is watching over it but I'll ping
the infrastructure team as well.
--
Ned Deily,
n...@acm.org
___
Python-Dev mailing list
As of the moment, buildbot.python.org seems to be down again. Where is
the best place to report problems like this?
--
Ned Deily,
n...@acm.org
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
h
Antoine and Martin and they are agreeable with that. So I think there
is general agreement that the infrastructure team can take on uptime
monitoring and rebooting of buildbot.python.org and that Antoine/Martin
would be the primary/secondary contacts/owners for other administrative
issues. Mar
e.
>
> Embracing pip upstream for Python 2 as well as Python 3 also sends a
> powerful signal to redistributors that says "your users are going to need
> this" and makes them do additional work to *avoid* providing it. Some of
> them *will* choose that path, but that becomes a
As I've already discussed with Larry, I think adding a week to the
scheduled dates would be preferable. The original dates give pretty
short notice and there are a number of open issues that would be good to
resolve now in 3.4.2.
--
Ned Deily,
n...@acm.org
__
9 as well.
--
Ned Deily,
n...@acm.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
.7.x is not "security only" and wouldn't reach that stage until 2020
under current policy.
http://legacy.python.org/dev/peps/pep-0373/#id5
https://docs.python.org/devguide/devcycle.html#branches
--
Ned Deily,
n...@acm.org
release of the Python 2.6 series. With its release on October 29,
2013, all official support for Python 2.6 has ended. Python 2.6
is no longer being maintained for any purpose."
http://legacy.python.org/dev/peps/pep-0361/
--
Ned Deily,
n...@acm.org
In article
,
Zachary Ware wrote:
> On Mon, Oct 6, 2014 at 12:24 PM, Ned Deily wrote:
> > 3. security: "fixing issues exploitable by attackers such as crashes,
> > privilege escalation and, optionally, other issues such as denial of
> > service attacks. Any other ch
king fine.
https://github.com/python/pythondotorg/issues/167
--
Ned Deily,
n...@acm.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-d
quickly disappears.
> Further if you navigate from 3.4.1 to 3.4.2 it says "Python 3.4.2rc1 was
> released on October 8th, 2014.". The download itself is correct.
Those two problems should be gone now. Thanks.
--
Ned Deily,
n...@acm.org
__
clone --uncompressed -U https://hg.python.org/cpython cpython
streaming all changes
10404 files to transfer, 248 MB of data
transferred 248 MB in 44.4 seconds (5.58 MB/sec)
--
Ned Deily,
n...@acm.org
___
Python-Dev mailing list
Pyth
In article ,
Ned Deily wrote:
> In article ,
> David Bolen wrote:
> > So that's sort of strange.
> Very interesting! I had been doing some housekeeping on some of my
> older OS X build systems over the past few days and I've run into the
> same problem.
ers mailing list:
http://packages.ubuntu.com/source/utopic/python-defaults
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Perhaps someone more familiar with the Ubuntu dev process will have a
better suggestion.
--
Ned Deily,
n...@acm.org
___
open an issue on the
website github issue tracker.
--
Ned Deily,
n...@acm.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
goal is to make it easier for newcomers to
contribute via pull requests, perhaps that field could be better
documented (like adding specific instructions to a readme on the
Bitbucket read-only mirror) or improved, if necessary.
https://docs.python.org/devguide/triaging.html#mercurial-re
about issue
tracker aren't a major concern for them. The dev guide does get issues
opened about it and I suppose they could be managed. But, without
tackling the CPython repo workflow (a *much* bigger deal), is the
divergence in workflows worth it? I dunno.
--
Ned Deily,
n...@ac
for each release. Until we start
shipping our own version of Tcl/Tk for OS X (which has been in the
cards), I don't think we can make it much easier.
--
Ned Deily,
n...@acm.org
___
Python-Dev mailing list
Python-Dev@python.org
https://mai
py of libffi that's used is based on the one in
PyObjC, which in turn is based on the version of libffi on
opensource.apple.com (IIRC with some small patches that fix minor issues
found by the PyObjC testsuite)."
--
Ned Deily,
n...@acm.org
__
h should be made easier.
Christophe, if you want to pursue this, you should open an issue for it
on the Python bug tracker, bugs.python.org. Otherwise, it will likely
be forgotten here.
--
Ned Deily,
n...@acm.org
___
Python-Dev mailing list
Python-De
upport.apple.com/en-us/HT201642
As described there, codesigned applications are automatically authorized
to accept inbound connections; that's the workaround proposed in the
apple.stackexchange cite. But arbitrarily signing development binaries
after every compile is probably n
1, we create the 3.5 branch. The 3.5 branch is 3.5.0 and
> trunk is 3.5.1. Only blessed stuff gets cherry-picked from 3.5.1 back into
> 3.5.0.
Where does 3.6.x fit into Workflow 2?
--
Ned Deily
n...@acm.org -- []
___
Python-Dev mailing li
On May 12, 2015, at 10:38, Larry Hastings wrote:
> On 05/12/2015 10:23 AM, Ned Deily wrote:
>> One possible issue with Workflow 1 is that there would need to be an
>> additional set of buildbots (for 3.5, in addition to the existing 3.x (AKA
>> "trunk"), 3.4, an
typically very short rc cycle of a maintenance
release and even then we usually see at most a couple of rc fixes and
usually none, as expected.
--
Ned Deily,
n...@acm.org
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/m
test/test_trace.py", line 305,
in _coverage
tracer.run(cmd)
File "/py/dev/3x/root/uxd/lib/python3.5/trace.py", line 500, in run
self.runctx(cmd, dict, dict)
File "/py/dev/3x/root/uxd/lib/python3.5/trace.py", line 508, in runctx
exec(cmd, glob
enance and feature branches (currently, master->3.7, 3.6, 2.7) on
docs.python.org are updated every 3 hours and, in theory, the downloadable
versions are updated once a day. But take that with a grain of salt (nudge
nudge, wink wink).
--
process and to make it easier for Windows and
Macs users to help test. Many new features and build changes are yet to appear
in subsequent releases prior to feature code cutoff on 2018-01-29 at 3.7.0b1.
Thanks for your help!
--Ned
--
Ned Deily
out it, please contact me directly. AFAIK,
there is no other release calendar feed currently.
--
Ned Deily
n...@python.org -- []
> On Sep 13, 2017, at 09:57, Fred Drake wrote:
>
>> On Wed, Sep 13, 2017 at 12:35 PM, Ned Deily wrote:
>> Lots of releases coming up so
ing system
releases and some tests may fail. If you are still using Python 3.3.x,
we **strongly** encourage you to upgrade now to a more recent, fully
supported version of Python 3. You can find Python 3.3.7 here:
https://www.python.org/downloads/release/python-337/
--
Ned Deily
n...@
The next maintenance release of Python 3.6 is expected to follow in
about 3 months, around the end of 2017-12. More information about the
3.6 release schedule can be found here:
https://www.python.org/dev/peps/pep-0494/
Enjoy!
--
Ned Deily
n...@
a preview release and its use is not recommended for
production environments. The next preview, 3.7.0a3, is planned for
2017-11-27. You can find Python 3.7.0a2 and more information here:
https://www.python.org/downloads/release/python-370a2/
--
Ned Deily
n...@python.org
ing
efforts!
--Ned
--
Ned Deily
n...@python.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
tackle that yet. Patches welome.
--
Ned Deily
n...@python.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
rastructure-team
--
Ned Deily
n...@python.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
maintenance release release
candidate, 3.6.4rc1. So I hope you can take advantage of the extra days for
both release cycles.
Thanks again for all your efforts!
--Ned
--
Ned Deily
n...@python.org -- []
___
Python-Dev mailing list
Python-Dev
adequately reviewed and
ready to go, go for it; likewise for normal bug fixes and doc changes. But
keep in the mind that there is still one more alpha preview release coming
prior to the beta 1 feature code freeze, so no need to panic.
--
Ned Deily
n...@python.org
/
--
Ned Deily
n...@python.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
to be an absolute necessity,
and the PEP needs to address exactly what sort of buildbot requirements make
sense here: emulators, SDKs, etc. Otherwise, we run the risk of ending up with
an ongoing
maintenance headache and unhappy users, as has been the case
The next maintenance release of Python 3.6 is expected to follow in
about 3 months, around the end of 2018-03. More information about the
3.6 release schedule can be found here:
https://www.python.org/dev/peps/pep-0494/
Enjoy!
--
Ned Deily
n...@
preview release and its use is not recommended for
production environments. The next preview release, 3.7.0b1, is planned
for 2018-01-29. You can find Python 3.7.0a4 and more information here:
https://www.python.org/downloads/release/python-370a4/
--
Ned Deily
n...@python.org
opinions about trust store and policies.
>
> Let's keep build dependencies a downstream and vendor problem.
That's not always an option, unfortunately.
--
Ned Deily
n...@python.org -- []
___
Python-Dev mailing list
Python-Dev@pytho
https://www.python.org/dev/peps/pep-0537/
--
Ned Deily
n...@python.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
specially
those of you merging code. Just because the CI tests passed doesn't mean there
won't be problems on other platforms and configurations.
Thanks for everyone's help so far! We're getting close.
--
Ned Deily
n...@python.org -- []
) are unaffected.
Thanks for your patience!
--
Ned Deily
n...@python.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%4
Here we are: 3.7.0b1 and feature code freeze! Congratulations and
thanks to all of you who've contributed to the huge number of PEPs,
features, bug fixes, and doc changes that have gone into 3.7 since
feature development began back in September 2016, after 3.6.0b1,
3.6's feature freeze. Now that fe
n be found here:
https://www.python.org/dev/peps/pep-0537/
--
Ned Deily
n...@python.org -- []
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mailman/opt
> python 4 going to be another python 3?
At this point, Python 4 is just a convenient tag for really big changes. There
are no concrete plans or schedule for such a major undertaking. Port away to
Python 3.x!
--
Ned Deily
n...@python.org -- []
after 3.7.0b3 without further discussion.
Thanks again for all of your hard work towards making 3.7.0 yet another
great release!
--Ned
--
Ned Deily
n...@python.org -- []
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/lis
nd here:
https://www.python.org/dev/peps/pep-0537/
--
Ned Deily
n...@python.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
018-12, 6 months after 3.7.0 releases and 2 years after 3.6.0 first released.
Thereafter, only security issues will be accepted and addressed for the
remaining life of 3.6.
Thanks again!
--Ned
https://www.python.org/dev/peps/pep-0494/
--
time I submitted the Pull requests, but I was wondering
> when the Labels get reset.
I've reset both manually. Thanks for the heads up. Now to get reviews!
--
Ned Deily
n...@python.org -- []
___
Python-Dev mailing list
Python-Dev@python.o
/release/python-365rc1/
Attention macOS users: as of 3.6.5rc1, there is a new additional installer
variant for macOS 10.9+ that includes a built-in version of Tcl/Tk 8.6.
This variant is expected to become the default variant in future releases.
Check it out!
--
Ned Deily
n...@python.org
ing PRs
for 3.7 (and please do!), be on the lookout for and flag potential
incompatibilities (we've all made them).
Thanks again for all of your hard work towards making 3.7.0 yet
another great release!
--Ned
--
Ned Deily
n...@python.org -- []
___
the bundled wheels are not present in the source
directory. Assuming that people building from a cpython repo need to have a
network connection if they want to run ensurepip, at least for the first time,
is probably not an onerous requirement.
--
Ned Deily
n..
https://www.python.org/psf/
--
Ned Deily
n...@python.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
ore information about the release schedule
can be found here:
https://www.python.org/dev/peps/pep-0537/
--
Ned Deily
n...@python.org -- []
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsu
You are not alone. There have been intermittent TLS connection issues with
bugs.python.org for some time now. The issue is being tracked here:
https://github.com/python/psf-infra-meta/issues/4
--
Ned Deily
n...@python.org -- []
___
Python-Dev
On Apr 4, 2018, at 12:59, Ned Deily wrote:
> On Apr 4, 2018, at 07:21, Agnostic Dev wrote:
>> Apologies if this is not the correct place to report this, but I am seeing
>> outages on bugs.python.org.
>> I am in the Chicago area so maybe this is a regional issue or possibly
r=&activity=&%40columns=activity&%40sort=activity&actor=&nosy=&type=&components=&versions=&dependencies=&assignee=&keywords=&priority=&status=1&%40columns=status&resolution=&nosy_count=&message_count=&
will show up.
Modifying GitHub Labels is only available to people with commit privs and,
IIRC, Skip asked to drop his commit privs a few years ago (although I'm sure we
would all be happy to welcome him back!).
> I'm afraid someone might have to intervene
r, 3.7, etc, requiring a merge or rebase, but you don't want to do
that since the change is already upstream.
Once the PR is merged into the main cpython repo, you can fix the problem by
force removing the original commit(s) from the "normal" branch in yo
ommenters on the issue consider the behavior to be a bug so
a case could be made for a fix to go into a maintenance release, not just a
feature release. But, obviously, someone needs to produce a PR for review
first.
--
Ned Deily
n...@python.org -- []
___
Thanks!
--Ned
https://docs.python.org/3.8/library/cmd.html
https://pypi.org/project/cmd2/
https://cmd2.readthedocs.io/
=-
Ned Deily
n...@python.org -- []
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python
find some answers to some of these questions there already.
--
Ned Deily
n...@python.org -- []
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mailman/optio
__()`. Whether that "should be" fatal, I don't know, but
> it's at least annoying ;-)
Prior art: COBOL uses "GIVING", as in:
ADD x, y GIVING z
No need to re-invent the wheel ;)
--
Ned Deily
n...@python.org -- []
_
potential incompatibilities (we've all
made them).
Thanks again for all of your hard work towards making 3.7.0 yet
another great release - coming to a website near you on 06-15!
--Ned
--
Ned Deily
n...@python.org -- []
___
Python-Dev
out!
The next preview release will be the release candidate and is planned
for 2018-05-21 followed by the official release of 3.7.0, planned for
2018-06-15. You can find Python 3.7.0b4 and more information here:
https://www.python.org/downloads/release/python-370b4/
--
Ned Deily
n...@python.org
benchmarks of static vs shared to the list so we can
>>> discuss it.
>> I have no idea what our default builds do on macOS, I'll let Ned Deily
>> or another mac expert answer (changing the topic in the hope he notices
>> this subthread :-)).
> And thanks for doin
o!), be on
the lookout for and flag potential incompatibilities (we've all made
them).
Thanks again for all of your hard work towards making 3.7.0 yet
another great release - coming to a website near you on 06-15!
Release Managerly Yours,
--Ned
https://www.python.org/de
much attention right away as we're
busy at the moment trying to get 3.7.0 out the door. And it would be best to
avoid including generated files (like configure vs configure.ac) in new PRs as
that will only add to the likelihood of merge conflicts and review complexity.
Thanks!
-
Ned Deil
of 2020-01-01.
There is more information later elsewhere in the devguide:
https://devguide.python.org/devcycle/
and in the release PEPs linked in the Status of Python Branches section.
Hope that helps!
--
Ned Deily
n...@python.org -- []
___
Python-Dev m
to support newer OS releases
and/or newer hardware support and receive no buildbot testing. Security mode
releases today are really for downstream distributors and DIYers who are
comfortable building and maintaining their own versions of software.
--
Ned Deily
n...@python.org -- []
___
Elvis has been working on the What’s New doc at the sprints this week. He
should be checking in his edits soon. Stay tuned!
--
Ned Deily
n...@python.org -- []
> On May 17, 2018, at 14:31, Serhiy Storchaka wrote:
>
> 15.05.18 14:51, Ned Deily пише:
>> This is it!
07:51, Ned Deily wrote:
> This is it! We are down to THE FINAL WEEK for 3.7.0! Please get your
> feature fixes, bug fixes, and documentation updates in before
> 2018-05-21 ~23:59 Anywhere on Earth (UTC-12:00). That's about 7 days
> from now. We will then tag and produce the 3.7.0 re
On May 21, 2018, at 08:41, Serhiy Storchaka wrote:
> Please don't forgot to perform the following steps when add a new public C
> API:
> [...]
Perhaps this should be added to the Python Developer's Guide?
--
Ned Deil
can and should be
backported, so having all active branches available in a local repo is a pretty
much a necessity.
As always, the Developer's Guide should be able to answer questions like this:
https://devguide.python.org/devcycle/
--
Ned Deily
n...@python.org -- []
On May 23, 2018, at 07:45, Serhiy Storchaka wrote:
> 15.05.18 14:51, Ned Deily пише:
>> This is it! We are down to THE FINAL WEEK for 3.7.0! Please get your
>> feature fixes, bug fixes, and documentation updates in before
>> 2018-05-21 ~23:59 Anywhere on Earth (UTC-12:00)
On May 23, 2018, at 09:13, Ned Deily wrote:
> On May 23, 2018, at 07:45, Serhiy Storchaka wrote:
>> Is it possible to add yet one beta instead?
>> CI was broken for few latest days, tests are not passed on my computer still
>> (and fail on some buildbots), updating W
On May 24, 2018, at 07:26, Victor Stinner wrote:
> 2018-05-24 9:23 GMT+02:00 Ned Deily :
>> Any merges to the 3.7 branch after
>> that will be released in 3.7.1 which we tentatively are planning to
>> ship sometime before the end of July (< 2018-07-31).
> I recall th
ase blocker"?
--
Ned Deily
n...@python.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
On May 24, 2018, at 12:26, Serhiy Storchaka wrote:
> 24.05.18 19:02, Ned Deily пише:
>> On May 24, 2018, at 11:35, Serhiy Storchaka wrote:
>>> I have doubts about two issues. I feel the responsibility for them because
>>> I had the opportunity to solve
On May 24, 2018, at 03:23, Ned Deily wrote:
> On May 23, 2018, at 09:13, Ned Deily wrote:
>> On May 23, 2018, at 07:45, Serhiy Storchaka wrote:
>>> Is it possible to add yet one beta instead?
>>> CI was broken for few latest days, tests are not passed on my computer
On May 28, 2018, at 05:05, Victor Stinner wrote:
> Ned Deily closed old bugs reported on the macOS Tiger buildbot, since
> this buildbot has been retired 3 months ago (the builders are still
> visible online, but last builds were 3 months ago).
Perhaps Zach or someone else can remove
gt;
> > For example my PR https://github.com/python/cpython/pull/7120 which
> > changes Lib/test/regrtest.py cannot be merged because a commit
> > touching the documentation (Doc/ directory) has been merged after I
> > posted my PR and before the CI completed.
> >
> > I don
On May 28, 2018, at 17:42, Victor Stinner wrote:
> 2018-05-28 19:47 GMT+02:00 Ned Deily :
>> Hmm, for some some reason, it appears that, at the moment, the 2.7, 3.4, and
>> 3.5 branches have that option set, while 3.6, 3.7, and master don't. I'm
>> not sure how w
time to work on making
Python better. I, for one, am deeply grateful.
2018-05-30 3.7.0b5
2018-06-11 3.7.0rc1 & 3.6.6rc1
2018-06-27 3.7.0final & 3.6.6final
--Ned
On May 25, 2018, at 01:33, Ned Deily wrote:
> On May 24, 2018, at 03:23, Ned Deily wrote:
>> On May 23, 2018, at 0
06-11, followed by the official
release of 3.7.0, now planned for 2018-06-27. You can find Python 3.7.0b5
and more information here:
https://www.python.org/downloads/release/python-370b5/
--
Ned Deily
n...@python.org -- []
___
Python-Dev mailing
27;s up to Ned.
I'd hate for 3.7 to fall behind in the emoji race :) Seriously, there are some
important additions that will, no doubt, appear in platforms over the lifetime
of 3.7 and the risk is very low. Thanks for pinging about it.
https://github.com/pytho
and buildbot test failures and see if you can help
resolve them. As always, if you think you may have found a critical
problem at any time in either release candidate, please open (or reuse)
an issue on bugs.python.org and mark it as "release blocker" priority.
3.7.0: here we c
06-27 3.7.0 final !!! and 3.6.6 final !!
- 2018-07-xx 3.7.1
- 2018-09-xx 3.6.7
--
Ned Deily
n...@python.org -- []
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.o
://www.python.org/downloads/release/python-366rc1/
--
Ned Deily
n...@python.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
, for example when trying to
merge a PR, please try again in a few hours.
Thanks and more later!
https://bugs.python.org/issue33851
https://bugs.python.org/issue33932
--
Ned Deily
n...@python.org -- []
___
Python-Dev mailing list
Python-Dev
e critical
fixes after rc1; usually there are very few.
--
Ned Deily,
n...@acm.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
z) are missing ...
They seem to be there now. Are you still not able to download them?
--
Ned Deily,
n...@acm.org
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.or
> On Jun 1, 2015, at 11:04, Yury Selivanov wrote:
>
> It looks like we now have two 3.6 release PEPs: 494 & 495
Sorry about the confusion. The second checkin (for 495) has been reverted; PEP
494 will be the ongoing PEP.
___
Python-Dev mailing list
1 - 100 of 468 matches
Mail list logo
