It’s with great pleasure that I announce that python-docs-theme has been
released to PyPI.
Thanks to the hard work and patience of Olga Bulat, @obulat, Python’s doc theme
is now responsive. Many thanks to everyone who has contributed to this release
by filing issues, writing PRs, reviewing PRs,
Thanks Tim.
On Tue, May 4, 2021, 11:13 AM Tim Peters wrote:
> FYI, I just force-unsubscribed this member (Hoi Lam Poon) from
> python-dev. Normally I don't do things like that, since, e.g, we have
> no way to know whether the sender address was spoofed in emails we
> get. But in this case Hoi'
Raymond,
Anyone can contribute to the documentation and comment, and core devs can
accept patches. Nothing changes here.
The Steering Council did approve the initial members and charter. The
intent has always been to be transparent and open. As discussed at last
year's Language Summit, the goal
Hi Raymond,
In about a month after the Language Summit, we'll have an open call for
applications for the Docs Workgroup similar to how the PSF gets and reviews
applications for the Code of Conduct workgroup.
Please keep an eye out for an announcement on Discourse, Python-Dev, and
the docs-communi
Luciano,
Thank you for such a thoughtful and eloquent response. Your wisdom is
definitely appreciated, and I agree this is an opportunity to go forward
with more clarity. I'm so proud of the Python dev community for their
thoughtful and respectful conversation.
All, Without the efforts of Larry,
Martin,
The decision regarding the action and email was unanimous (5-0). It was
discussed in our March 15 and March 22 Steering Council meeting.
This post and this other post (
https://mail.python.org/archives/list/python-dev@python.org/message/J5GR6YVIVWQ2VPLISAGBQH3UQN4YWAXS/)
provides context
GitLab has just posted the following re: default branches.
https://about.gitlab.com/blog/2021/03/10/new-git-default-branch-name/
Please take a moment to pause before posting. Please consider whether
additional comments are constructive. I'm concerned that rehashing the same
arguments will reflect
I echo Barry's earlier response.
To directly address individuals who object to renaming the branch: I
respect your opinion. As I weigh the benefits of keeping the status quo
with the benefits of changing, I see the change as a temporary
inconvenience to update the branch once in order to open the
Hi Julien,
I think that there are two items to consider:
- `needs_sphinx` in `conf.py`
- setting for Sphinx in `cpython/Doc/requirements.txt`
I believe that the `needs_sphinx` field identifies the minimal version of
Sphinx that can be used to build the docs. The actual version that is used
to bui
On Tue, Dec 8, 2020 at 7:32 AM Paul Moore wrote:
> On Tue, 8 Dec 2020 at 15:19, David Mertz wrote:
> >
> > As a candidate for the new SC, if elected I would certainly find it more
> useful to have more specific thoughts from the outgoing SC than simply "we
> recommend." How divided was the vote?
On Tue, Nov 10, 2020 at 8:07 AM Mats Wichmann wrote:
> On 11/9/20 12:46 PM, Mike Miller wrote:
> >
> > On 2020-11-09 10:44, Simon Cross wrote:
> >> That's quite subjective. Personally I prefer a more complete tutorial
> >> which explains many details so that I don't immediately run into
> >> fund
We'll be making an announcement in a few weeks asking folks to apply for
the workgroup. The workgroup will be at most 20 people with the goal of
having significant representation (25% to 50%) of individuals who are
educators and documentarians. One goal of the workgroup is to set
documentation prio
Thanks Inada-san for bringing up this issue. I agree with your point and
Guido's that the tutorial should target learning Python if new to the
language but not coding. It's likely that in the future there will be an
even more basic tutorial for those newer to coding.
An advanced concept, as Kyle m
On Sat, Oct 10, 2020 at 10:42 AM Jeff Allen wrote:
> On 10/10/2020 00:56, Brett Cannon wrote:
>
> On Fri, Oct 9, 2020 at 2:55 PM Toshio Kuratomi wrote:
>
>>
>> One thing i would suggest, though, is documenting and, in general,
>> following a sequence of progressively more strict interventions by
On Fri, Oct 9, 2020 at 2:50 PM Toshio Kuratomi wrote:
>
>
> On Fri, Oct 9, 2020, 5:30 AM Christian Heimes
> wrote:
>
>> On 09/10/2020 04.04, Ivan Pozdeev via Python-Dev wrote:
>> > I don't see the point of requiring to "write an apology", especially
>> > *before a 12-month ban*. If they understa
Hi folks,
Thanks for the interest. I apologize for the delay in getting this
workgroup started. I'm happy that there is strong interest in working on
documentation and improving it for all users.
I will do my best to get the workgroup charter drafted this week and then
open an interest list for i
Hi folks,
Earlier this year at the Python Language Summit, Ned Batchelder and I presented
the concept of a Documentation Workgroup and a vision for the next few years:
- Slidedeck
https://speakerdeck.com/willingc/cpython-documentation-the-next-5-years
- Blog post
https://pyfound.blogspot.com/2
o do the nominating. Brett Cannon and Carol Willing have posted about
> what the work entails:
>
> https://snarky.ca/what-its-like-to-be-on-the-python-steering-council/
> https://www.willingconsulting.com/post/2019-11-02-python-steering-retro/
>
> If you think you might be intereste
Hi Simon,
There are several ways to share constructive feedback. You may email the
steering council, file an issue on the public steering council repo, or create
a discussion thread on Discourse or python-dev.
Thanks!
Carol
On Mon, Jul 8, 2019, at 12:35 PM, Simon Cross wrote:
> Is there a way
Sorry for the incorrect link. Here is the corrected link:
https://github.com/python/steering-council/blob/master/updates/2019-07-08_steering-council-update.md
On Mon, Jul 8, 2019, at 7:16 AM, Carol Willing wrote:
> I've posted an update from the Steering Council to our repo:
I've posted an update from the Steering Council to our repo:
https://github.com/python/steering-council/blob/master/updates/2019-07-08_steering-council
I will also link to this on python-dev and on Discourse (discuss.python.org ).
For completeness, below is the full text.
# Steering Council U
ython.org/
> Message archived at
> https://mail.python.org/archives/list/python-dev@python.org/message/JPWPWUUYDRWNWALTVT4VIT4L6WMBNIRJ/
>
--
*Carol Willing*
Willing Consulting <https://willingconsulting.com>
*Signature strengths*
*Empathy - Relator - Ideation - Strategic - Learner*
_
Hi Phil,
Thanks for trying the beta. Please file this as an issue at
bugs.python.org. Doing so would be helpful for folks who can look into
the issue.
Thanks,
Carol
On 6/22/19 2:04 PM, Phil Thompson wrote:
The implementation of issue 36085 breaks PyQt on Windows as it relies
on PATH to fin
Barry Warsaw wrote on 6/5/19 10:56 AM:
On Jun 5, 2019, at 02:08, Victor Stinner wrote:
Our kind postmasters Mark Sapiro and Abhilash Raj migrated
python-ideas and python-dev mailing lists from Mailman 2 to Mailman 3
(running on Python 3 ;-))!
Gosh, it warms my heart. :)
Thank you Mark, Abhi
Nathaniel Smith wrote:
On Fri, May 31, 2019 at 11:39 AM Barry Warsaw wrote:
On May 31, 2019, at 01:22, Antoine Pitrou wrote:
I second this.
There are currently ~7000 bugs open on bugs.python.org. The Web UI
makes a good job of actually being able to navigate through these bugs,
searc
Sorry for the inconvenience yesterday.
___
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
The Python Steering Council is pleased to provide an update to the Python
community about Steering Council activity and CPython development. We've
created a GitHub repo for Steering Council updates and helpful documents:
https://github.com/python/steering-council
Here's the latest update writte
is
a good idea or if this is just late night caffeine talking.
I have absolutely no problem if you want to pitch this idea to new
contributors who show up at the sprints!
-Brett
Camilla,
I would be happy to support your effort. I find it a wonderful idea!
Carol
Carol Willing
Research Softwar
On 8/18/15 7:52 AM, R. David Murray wrote:
On Tue, 18 Aug 2015 12:47:22 +1000, Ben Finney
wrote:
Robert Collins writes:
However - 9 isn't a bad number for 'patches that the triagers think
are ready to commit' inventory.
So yay!. Also - triagers, thank you for feeding patches through the
On 7/26/15 6:37 PM, R. David Murray wrote:
On Sun, 26 Jul 2015 22:59:51 +0100, Paul Moore wrote:
On 26 July 2015 at 16:39, Berker PeksaÄŸ wrote:
So, I'm hoping Carol will take what I've written above and turn it into
updates for the devguide (assuming no one disagrees with what I've said :)
On 7/21/15 9:31 PM, Nick Coghlan wrote:
On 22 July 2015 at 04:08, Brett Cannon wrote:
On Tue, Jul 21, 2015 at 11:05 AM Carol Willing
wrote:
The Communications Quick Start section would be brief and practical much
like the Quick Start section for downloading and testing the source
code
I would like to add a "Communications Quick Start" section to the
beginning of the Python Developer's Guide.
Productive communication between each other will always be critical to
future development of CPython and maintaining releases, infrastructure,
documentation, and more.
Unproductive co
. Practically, use whichever version
is best suited to the use case.
Warmly,
Carol
P.S. Whether you develop for version 2, version 3, or both, thank you
for doing so :-)
--
*Carol Willing*
Developer | Willing Consulting
https://willingconsulting.com
_
W9
I'm unaware of a way to work around this other than using Apple's code
signing or adjusting target build settings in XCode :( If anyone knows a
good way to workaround or manually set permission (other than clicking
the Allow button), I would be interested.
Warmly,
were new and magical. Looking at the Coverity scans, I'm glad that the
old magic is reaping real benefits.
--
*Carol Willing*
Developer | Willing Consulting
https://willingconsulting.com
___
Python-Dev mailing list
Python-Dev@python.org
https:
s set up correctly.
___
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/willingc%40willingconsulting.com
--
*Carol Willing*
Developer | Willing Consulting
https://wil
iling list
Python-Dev@python.org <mailto:Python-Dev@python.org>
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mailman/options/python-dev/guido%40python.org
--
--Guido van Rossum (python.org/~guido <http://python.org/%7Eguido>)
dev/willingc%40willingconsulting.com
--
*Carol Willing*
Developer | Willing Consulting
https://willingconsulting.com
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.or
took about 5 minutes to guide each user through
installing 3.4.1. The new 3.4.2rc1 installer is a *big* improvement.
It also seems as if launching the interpreter from the command line is
also faster now :)
--
*Carol Willing*
Developer | Willing Consulting
+1 760 456 9366 | https
39 matches
Mail list logo
