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
First - best wishes all for a happy and healthy 2020!
As my nickname implies - my primary means to contribute to Python is
with regard to AIX. One of the things I recently came across is
Misc/README.AIX which was last updated sometime between 2010 and 2014. I
am thinking a facelift is in order. As
On 4/20/2019 4:14 AM, Alessandro Cucci wrote:
Hello folks,
I want to start a project for translating the Python Documentation in
Italian.
I'm reading the PEP545, trying to understand how it works.
I founded a Python User Group in my city and I can work with them on the
translations, plus next
Hello folks,
I want to start a project for translating the Python Documentation in
Italian.
I'm reading the PEP545, trying to understand how it works.
I founded a Python User Group in my city and I can work with them on the
translations, plus next month I will be speaker at Pycon Italy, so I can
e
Nick Coghlan wrote:
> Benjamin Peterson wrote:
>> On Sun, Sep 21, 2008 at 2:12 PM, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
[...]
>>> In addition, some documentation set should show up at
>>>
>>> http://docs.python.org/
>>>
>>> Not sure whether this should be 2.6 or 3.0.
>> Almost certainly 2.6
Barry Warsaw schrieb:
> On Sep 21, 2008, at 6:03 AM, Georg Brandl wrote:
>
>> Barry Warsaw schrieb:
>>> Martin points out that in the past, as part of the release process,
>>> we've built separate downloadable documentation.
>>>
>>> Do we still want to do that for Python 2.6 and 3.0, and if so, ho
Benjamin Peterson wrote:
> On Sun, Sep 21, 2008 at 2:12 PM, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
>>> I notice that for 2.5, we zip'd and tar-bz2'd them. Do we want to also
>>> support tgz? We'll have to hack the release script to build the doc
>>> zips. I'll try to test drive this whole
On Sun, Sep 21, 2008 at 2:12 PM, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
>> I notice that for 2.5, we zip'd and tar-bz2'd them. Do we want to also
>> support tgz? We'll have to hack the release script to build the doc
>> zips. I'll try to test drive this whole process soon.
>
> In addition
> I notice that for 2.5, we zip'd and tar-bz2'd them. Do we want to also
> support tgz? We'll have to hack the release script to build the doc
> zips. I'll try to test drive this whole process soon.
In addition to the creation of downloadable scripts, there should also
be a copy of the document
On Sep 21, 2008, at 7:24 AM, Barry Warsaw wrote:
I notice that for 2.5, we zip'd and tar-bz2'd them. Do we want to
also support tgz? We'll have to hack the release script to build
the doc zips. I'll try to test drive this whole process soon.
We specifically decided to drop .tgz since it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 21, 2008, at 6:03 AM, Georg Brandl wrote:
Barry Warsaw schrieb:
Martin points out that in the past, as part of the release process,
we've built separate downloadable documentation.
Do we still want to do that for Python 2.6 and 3.0, and if
Barry Warsaw schrieb:
> Martin points out that in the past, as part of the release process,
> we've built separate downloadable documentation.
>
> Do we still want to do that for Python 2.6 and 3.0, and if so, how do
> we go about doing that? I have this feeling that building the
> documentation
+1.
I find the offline versions to be vital.
Sent from my iPhone
On Sep 19, 2008, at 12:20 PM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin points out that in the past, as part of the release process,
we've built separate downloadable documen
On Sep 19, 2008, at 7:20 AM, Barry Warsaw wrote:
Martin points out that in the past, as part of the release process,
we've built separate downloadable documentation.
Do we still want to do that for Python 2.6 and 3.0, ...?
Yes, I think so. The downloads are very useful for people who
regu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin points out that in the past, as part of the release process,
we've built separate downloadable documentation.
Do we still want to do that for Python 2.6 and 3.0, and if so, how do
we go about doing that? I have this feeling that building
Python Doc Problem Example: os.path.split()
Xah Lee, 20050918
Quote from: http://www.python.org/doc/2.4.1/lib/module-os.path.html
«
split(path)
Split the pathname path into a pair, (head, tail) where tail is
the last pathname component and head is everything leading up to
that. The
16 matches
Mail list logo
