[Python-Dev] Re: Inline links in Misc/NEWS entries

[Michael]

On 16/08/2019 05:31, Kyle Stanley wrote:
> Yeah definitely, it was my intention to mention this in the devguide,
> particularly with adding an example of the Sphinx roles being used and
> explaining appropriate usage. I hadn't thought of linking to the list of
> roles (https://devguide.python.org/documenting/#id4), but that's definitely
> a good idea to include. I was just waiting for everyone to get a chance to
> provide feedback on the topic before expanding the devguide.
>
> After the devguide is updated, I was also planning on adding the markup to
> 3.8's Misc/NEWS entries (in the appropriate branch, as Ned recommended),
> and then work on the 3.9. I'll probably split it into several smaller PRs
> so it's easier to review.

There has been "a lot" of discussion re: things for new contributors to
do and learn.

a) this seems to be "well-defined", and imho, suitable as "easy", etc..
b) isn't this something we want new people to be more aware of (as you
said, you have been working with this for a year)
c) it is an area (Documentation) I have clearly 'missed' as I focused on
'other things', and, with myself and many projects I have worked on over
the years - Documentation seems to come in last. Getting new (and
newish, as myself) working here only makes us better suited for review
in the future.

So, I guess this is an area where you could "mentor", perhaps create
"issues" that specify the "paragraphs", or whatever you think are
appropriate 'chunks' to make review sensible (if not also easier).

Michael




signature.asc
Description: OpenPGP digital signature
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/python-dev@python.org/message/T5YQW2I624S7UU63AXNBNGOH7ASF6OWC/

[Python-Dev] Re: [Webmaster] Python for Mac OS X Catalina

[Steve Holden]

Hi Ana,

This is something that the development team are best placed to answer, and
I'm sure that they'd be happy to know if there are bumps in the road coming
up with Catalina.

I am copying this reply to the core developer list to alert them. It would
be helpful if you could make as full a report as possible via
bugs.python.org. A reply-all to this email can be used to let the
development team know the report reference should you do so, and the bug
tracker is a better medium for such focused communication than the list.

I've moved the webmaster address to Bcc to relieve it of further traffic.
Good luck!

Steve Holden


On Fri, Aug 16, 2019 at 11:04 AM Ana Simion via Webmaster <
webmas...@python.org> wrote:

> Hello,
>
> Can you advise when you’re going to update Python to work with Mac OS X
> Catalina? I am running the beta of  Mac OS X Catalina but am unable to
> install the python software - I get a message advising the Developer hasn’t
> updated the software to work with the new OS yet. I’d be most grateful if
> you could get back to me as soon as possible.
>
> Many thanks
>
> Ana Simion
>
>
> ___
> Webmaster mailing list
> webmas...@python.org
> https://mail.python.org/mailman/listinfo/webmaster
>
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/python-dev@python.org/message/CA3S22D63KY3K5ZOT2SDKBDEV5ICOOT4/

[Python-Dev] Re: [Webmaster] Python for Mac OS X Catalina

[Ronald Oussoren via Python-Dev]

Hi,

As a workaround it is possible to install Python by choosing “open” from the 
context-menu of in the Finder instead of double clicking on the installer.   
This is currently necessary because the macOS Catalina has stricter 
requirements for signing installers, and the Python.org  
installers do not yet comply with those stricter requirements.

Ronald
—

Twitter: @ronaldoussoren
Blog: https://blog.ronaldoussoren.net/

> On 16 Aug 2019, at 13:24, Steve Holden  wrote:
> 
> Hi Ana,
> 
> This is something that the development team are best placed to answer, and 
> I'm sure that they'd be happy to know if there are bumps in the road coming 
> up with Catalina.
> 
> I am copying this reply to the core developer list to alert them. It would be 
> helpful if you could make as full a report as possible via bugs.python.org 
> . A reply-all to this email can be used to let the 
> development team know the report reference should you do so, and the bug 
> tracker is a better medium for such focused communication than the list.
> 
> I've moved the webmaster address to Bcc to relieve it of further traffic. 
> Good luck!
> 
> Steve Holden
> 
> 
> On Fri, Aug 16, 2019 at 11:04 AM Ana Simion via Webmaster 
> mailto:webmas...@python.org>> wrote:
> Hello, 
> 
> Can you advise when you’re going to update Python to work with Mac OS X 
> Catalina? I am running the beta of  Mac OS X Catalina but am unable to 
> install the python software - I get a message advising the Developer hasn’t 
> updated the software to work with the new OS yet. I’d be most grateful if you 
> could get back to me as soon as possible.
> 
> Many thanks
> 
> Ana Simion
> 
> 
> ___
> Webmaster mailing list
> webmas...@python.org 
> https://mail.python.org/mailman/listinfo/webmaster 
> 
> ___
> Python-Dev mailing list -- python-dev@python.org
> To unsubscribe send an email to python-dev-le...@python.org
> https://mail.python.org/mailman3/lists/python-dev.python.org/
> Message archived at 
> https://mail.python.org/archives/list/python-dev@python.org/message/CA3S22D63KY3K5ZOT2SDKBDEV5ICOOT4/

___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/python-dev@python.org/message/UWKLIJMPDGIF2QJDLNHP5LXBWMJ74Q5A/

[Python-Dev] Re: [Webmaster] Python for Mac OS X Catalina

[Ned Deily]

On Aug 16, 2019, at 06:11, Ronald Oussoren via Python-Dev 
 wrote:
> As a workaround it is possible to install Python by choosing “open” from the 
> context-menu of in the Finder instead of double clicking on the installer.   
> This is currently necessary because the macOS Catalina has stricter 
> requirements for signing installers, and the Python.org installers do not yet 
> comply with those stricter requirements.


And we will be addressing this for current Python installers prior to the 
upcoming official release of macOS 10.15 Catalina.

  --
Ned Deily
n...@python.org -- []___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/python-dev@python.org/message/52QZRXLSUYCSXRFFB5EBE3J67ZN63PJI/

[Python-Dev] Summary of Python tracker Issues

[Python tracker]

ACTIVITY SUMMARY (2019-08-09 - 2019-08-16)
Python tracker at https://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:
  open7171 (+35)
  closed 42457 (+38)
  total  49628 (+73)

Open issues with patches: 2911 


Issues opened (56)
==

#15248: Better explain "TypeError: 'tuple' object is not callable"
https://bugs.python.org/issue15248  reopened by rhettinger

#34155: email.utils.parseaddr mistakenly parse an email
https://bugs.python.org/issue34155  reopened by vstinner

#37756: Error 0x80070643 when installing
https://bugs.python.org/issue37756  reopened by eryksun

#37805: json.dump(..., skipkeys=True) has no unit tests
https://bugs.python.org/issue37805  opened by Julian

#37806: Infinite recursion with typing.get_type_hints
https://bugs.python.org/issue37806  opened by vg0377467

#37808: Deprecate unbound super methods
https://bugs.python.org/issue37808  opened by steven.daprano

#37810: ndiff reports incorrect location when diff strings contain tab
https://bugs.python.org/issue37810  opened by Anthony Sottile

#37812: Make implicit returns explicit in longobject.c (in CHECK_SMALL
https://bugs.python.org/issue37812  opened by Greg Price

#37815: 'Make Test' error while trying to install Python 3.7.4 on Linu
https://bugs.python.org/issue37815  opened by Missono Dell

#37816: f-string documentation not fully accurate
https://bugs.python.org/issue37816  opened by v+python

#37817: create_pipe_connection and start_serving_pipe not documented
https://bugs.python.org/issue37817  opened by primal

#37820: Unnecessary URL scheme exists to allow 'URL: reading file in u
https://bugs.python.org/issue37820  opened by Alyan

#37821: IDLE shell uses wrong namespace for completions
https://bugs.python.org/issue37821  opened by taleinat

#37823: Telnet documentation: fix the link to open()
https://bugs.python.org/issue37823  opened by Mariatta

#37824: IDLE: Handle Shell input warnings properly.
https://bugs.python.org/issue37824  opened by serhiy.storchaka

#37825: IDLE doc improvements
https://bugs.python.org/issue37825  opened by terry.reedy

#37826: Document PEP 3134 in tutorials/errors.rst
https://bugs.python.org/issue37826  opened by maxking

#37827: IDLE: Have the shell mimic terminal handling of \r and \b cont
https://bugs.python.org/issue37827  opened by taleinat

#37828: Fix default mock_name in unittest.mock.assert_called error mes
https://bugs.python.org/issue37828  opened by xtreak

#37829: Documentation of stdlib: add example of mixed arguments to dic
https://bugs.python.org/issue37829  opened by pasenor

#37830: continue and break in finally with return in try results with 
https://bugs.python.org/issue37830  opened by BTaskaya

#37832: Python requires /dev/urandom on HURD: _Py_HashRandomization_In
https://bugs.python.org/issue37832  opened by Jeffrey.Walton

#37834: readlink on Windows cannot read app exec links
https://bugs.python.org/issue37834  opened by steve.dower

#37835: typing.get_type_hints wrong namespace for forward-declaration 
https://bugs.python.org/issue37835  opened by netbnd

#37836: Support .as_integer_ratio() in fractions.Fraction
https://bugs.python.org/issue37836  opened by jdemeyer

#37837: add internal _PyLong_FromUnsignedChar() function
https://bugs.python.org/issue37837  opened by sir-sigurd

#37838: typing.get_type_hints not working with forward-declaration and
https://bugs.python.org/issue37838  opened by netbnd

#37839: makesetup Doesn't Handle Defines with Equal Sign
https://bugs.python.org/issue37839  opened by wbond

#37840: bytearray_getitem() handles negative index incorrectly
https://bugs.python.org/issue37840  opened by sir-sigurd

#37841: Python store app launcher has dependency on msvcp140.dll
https://bugs.python.org/issue37841  opened by steve.dower

#37842: Initialize Py_buffer variables more efficiently
https://bugs.python.org/issue37842  opened by sir-sigurd

#37843: CGIHTTPRequestHandler does not take args.directory in construc
https://bugs.python.org/issue37843  opened by rjayne

#37844: PyRun_SimpleFile should provide a version that does not need a
https://bugs.python.org/issue37844  opened by cbiesinger

#37846: declare that Text I/O use buffer inside
https://bugs.python.org/issue37846  opened by Windson Yang

#37848: More fully implement Unicode's case mappings
https://bugs.python.org/issue37848  opened by Greg Price

#37849: IDLE: Completion window misplaced when shown above current lin
https://bugs.python.org/issue37849  opened by taleinat

#37851: faulthandler: only allocate the signal handler stack when faul
https://bugs.python.org/issue37851  opened by vstinner

#37854: [xmlrpc.client.ServerProxy] It does not correctly parse the UR
https://bugs.python.org/issue37854  opened by f9n

#37855: Compiling Python 3.7.4 with Intel compilers 2019
https://bugs.python.org/issue37855  opened by zyzhang2006

#37856: Adding additional python ins

[Python-Dev] Re: Inline links in Misc/NEWS entries

[Kyle Stanley]

> a) this seems to be "well-defined", and imho, suitable as "easy", etc..

Part of this could potentially be suitable as an "easy" issue, but I'm not
certain that it would make for a good first PR, since it is involving a
fairly important and widely used section of the devguide. Many newcomers
may not be familiar with what would be considered "appropriate usage" of
the Sphinx roles in news entries. When I think of issues that would be good
first PRs involving documentation, I generally think of grammar/spelling
improvements or perhaps more objective fixes. This section might be a
little bit too subjective though.

> b) isn't this something we want new people to be more aware of (as you
> said, you have been working with this for a year)

I think you might be confusing me with someone else, as I've only been
contributing to Python since June of this year. I've built up some amount
of experience from PRs I've submitted as well as PR reviews, but I would
still consider myself to be a more recent contributor. If I come across as
having more experience though, that's certainly a good thing. (:

> c) it is an area (Documentation) I have clearly 'missed' as I focused on
> 'other things', and, with myself and many projects I have worked on over
> the years - Documentation seems to come in last. Getting new (and
> newish, as myself) working here only makes us better suited for review
> in the future.

I definitely agree that we should try to come up with ways to improve the
interaction with the documentation (particularly with the devguide). A
great way to do that can be cleaning up existing sections, but for reasons
previously stated, I'm not certain that this issue is particularly well
suited for that. It's "well-defined" from feedback in the mailing list
discussion, but I think it would benefit from being written by someone with
some experience in news entries, reST and Sphinx markup, and documentation
in general.

However, a great way that anyone could help out would be through providing
feedback on the PR once it's open. Providing feedback on PRs is great way
to improve experience in an area, and also helps to deal with a major
bottleneck for Python development in general. We have far more people
submitting PRs than reviewers.

Once I open the PR for it in the devguide, I'll be sure to send a message
in this topic which includes a link to it. It would greatly benefit from
review from those who are less familiar with documentation. That will help
to ensure the section is easy to understand for the intended target
audience. Of course, it would also benefit from those are are experienced
as well, to ensure it is as accurate as possible.

Thanks,
Kyle Stanley

On Fri, Aug 16, 2019 at 4:48 AM Michael  wrote:

> On 16/08/2019 05:31, Kyle Stanley wrote:
> > Yeah definitely, it was my intention to mention this in the devguide,
> > particularly with adding an example of the Sphinx roles being used and
> > explaining appropriate usage. I hadn't thought of linking to the list of
> > roles (https://devguide.python.org/documenting/#id4), but that's
> definitely
> > a good idea to include. I was just waiting for everyone to get a chance
> to
> > provide feedback on the topic before expanding the devguide.
> >
> > After the devguide is updated, I was also planning on adding the markup
> to
> > 3.8's Misc/NEWS entries (in the appropriate branch, as Ned recommended),
> > and then work on the 3.9. I'll probably split it into several smaller PRs
> > so it's easier to review.
>
> There has been "a lot" of discussion re: things for new contributors to
> do and learn.
>
> a) this seems to be "well-defined", and imho, suitable as "easy", etc..
> b) isn't this something we want new people to be more aware of (as you
> said, you have been working with this for a year)
> c) it is an area (Documentation) I have clearly 'missed' as I focused on
> 'other things', and, with myself and many projects I have worked on over
> the years - Documentation seems to come in last. Getting new (and
> newish, as myself) working here only makes us better suited for review
> in the future.
>
> So, I guess this is an area where you could "mentor", perhaps create
> "issues" that specify the "paragraphs", or whatever you think are
> appropriate 'chunks' to make review sensible (if not also easier).
>
> Michael
>
>
>
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/python-dev@python.org/message/ROXFQX7ZDXFH5YRNGYZU3KCF7GR5QQLL/

[Python-Dev] Re: Inline links in Misc/NEWS entries

[Kyle Stanley]

Based on the feedback from the ML thread and Discuss topic, I created a new
PR on python/devguide which expands the "What's New and News Entries"
section of "committing.rst" to include Sphinx roles:
https://github.com/python/devguide/pull/525/files

I would greatly appreciate feedback from contributors and developers less
experienced with documentation to ensure that the section is easy to
understand for the intended target audience. Also, review from those who
are experienced with documentation and news entries is needed to ensure it
is as accurate as possible.

Thanks,
Kyle Stanley

On Mon, Aug 12, 2019 at 10:24 PM Kyle Stanley  wrote:

> Recently, on Discuss, I created a new topic:
> https://discuss.python.org/t/should-news-entries-contain-documentation-links/2127
>
> However, many may not have the time to read the full post or don’t
> regularly check the core workflow category on Discuss, so I'll provide a
> shortened version here.
>
> During my experience thus far reviewing PRs on GitHub, I've noticed a
> significant degree of inconsistency when it comes to the usage of inline
> links with reST and Sphinx in Misc/NEWS entries. Since many of my
> contributions have involved documentation changes, I've familiarized myself
> most of the syntax.
>
> Many of the features in markup languages provide visual modifications
> rather than functional ones. However, with the inline markup supported by
> reST and processing from Sphinx, there's a functional improvement as well.
> For example, the usage of :func:\`\` (escaped for mailman)
> provides a link to the relevant docs for the function.
>
> In the context of news entries, this allows readers to click on a
> function, method, class, etc for more information. This can be useful if
> it's something they're not familiar with, or when the changes affected the
> docs. For those who are familiar with the structure of docs.python.org,
> the cross link to the docs may not seem at all necessary.
>
> However, for readers that are either newer or not familiar with the
> structure, they might be led astray into 2.7 docs or an entirely wrong
> page. This happens especially frequently when using external search engines.
>
> I'm not at all suggesting that every PR author should be required to use
> it or know all of the reST constructs. However, I would like for everyone
> to be aware of the potential usefulness of including inline links in news
> entries, and mention it in the devguide.
>
> Also, I would like to understand why some developers dislike including it,
> even when the reST syntax is provided. The majority of authors so far would
> add my suggestion to their PR, but there have been some that don't want
> anything besides plaintext in their news entry.
>
> Personally, I think it provides further inclusiveness to readers of all
> levels of experience and QoL at a very minimal cost.
> ___
> Python-Dev mailing list -- python-dev@python.org
> To unsubscribe send an email to python-dev-le...@python.org
> https://mail.python.org/mailman3/lists/python-dev.python.org/
> Message archived at
> https://mail.python.org/archives/list/python-dev@python.org/message/HTAFGTQIZJQUCU6QCVF3KFD3VFGFOBWV/
>
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/python-dev@python.org/message/2VI4OZI7YTFUXW4LUETY3QYZ3TU6BU7J/