Please commit any PEP changes to hg.python.org/peps.
Also, sorry for the span on -checkins, I should not have enabled the notification hook before pushing all changes :)
Georg
In article <imdluc$u51$1@dough.gmane.org>, Georg Brandl <g.brandl@gmx.net> wrote:
Please commit any PEP changes to hg.python.org/peps.
Looks like the Version and Last-Modified keywords formerly supplied by svn are now AWOL on the generated web pages.
-- Ned Deily, nad@acm.org
On 24.03.2011 02:35, Ned Deily wrote:
In article <imdluc$u51$1@dough.gmane.org>, Georg Brandl <g.brandl@gmx.net> wrote:
Please commit any PEP changes to hg.python.org/peps.
Looks like the Version and Last-Modified keywords formerly supplied by svn are now AWOL on the generated web pages.
Thanks, I've fixed that now (by locally enabling the keyword extension).
Georg
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 24/03/11 09:12, Georg Brandl wrote:
On 24.03.2011 02:35, Ned Deily wrote:
In article <imdluc$u51$1@dough.gmane.org>, Georg Brandl <g.brandl@gmx.net> wrote:
Please commit any PEP changes to hg.python.org/peps.
Looks like the Version and Last-Modified keywords formerly supplied by svn are now AWOL on the generated web pages.
Thanks, I've fixed that now (by locally enabling the keyword extension).
These requirements (activate the keyword extension, and set it to "**.txt" files) should be documented somewhere... :).
BTW, can I actually push to "hg.python.org/peps", as indicated?. I would expect something like "ssh://hg@hg.python.org/peps".
Jesus Cea Avion _/_/ _/_/_/ _/_/_/ jcea@jcea.es - http://www.jcea.es/ _/_/ _/_/ _/_/ _/_/ _/_/ jabber / xmpp:jcea@jabber.org _/_/ _/_/ _/_/_/_/_/ . _/_/ _/_/ _/_/ _/_/ _/_/ "Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/ "My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/ "El amor es poner tu felicidad en la felicidad de otro" - Leibniz -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQCVAwUBTYuKF5lgi5GaxT1NAQKKtwP8DXMD02ocwHiHIJbnd2lr3bp8vbxx7HiF yTrBKH6LdqyNUHgorcvXtL5lzcrwqcg/ppOVtODHolM48GMM3hX0A44SAqjMMYoO YByRWmt5v/lOBaKfgW/mM2TEbDm7PeGkCh/zzBFVelA9fk2VNYZ1u8epb0lxFmwr g2K2MPqqRfY= =V7w3 -----END PGP SIGNATURE-----
On 24.03.2011 19:14, Jesus Cea wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 24/03/11 09:12, Georg Brandl wrote:
On 24.03.2011 02:35, Ned Deily wrote:
In article <imdluc$u51$1@dough.gmane.org>, Georg Brandl <g.brandl@gmx.net> wrote:
Please commit any PEP changes to hg.python.org/peps.
Looks like the Version and Last-Modified keywords formerly supplied by svn are now AWOL on the generated web pages.
Thanks, I've fixed that now (by locally enabling the keyword extension).
These requirements (activate the keyword extension, and set it to "**.txt" files) should be documented somewhere... :).
Well, I don't think it's required for anyone other than python.org. Those who edit the PEPs just need to keep the $Revision$ and $Date$ intact.
BTW, can I actually push to "hg.python.org/peps", as indicated?. I would expect something like "ssh://hg@hg.python.org/peps".
Yes, of course.
Georg
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 24/03/11 22:29, Georg Brandl wrote:
These requirements (activate the keyword extension, and set it to "**.txt" files) should be documented somewhere... :).
Well, I don't think it's required for anyone other than python.org. Those who edit the PEPs just need to keep the $Revision$ and $Date$ intact.
So, must I disable the extension KW again?. I am confused.
Maybe editors simply must keep "$Revision$" and "$Date$", since those keywords are expanded in the server, for showing in docs.python.org?.
Jesus Cea Avion _/_/ _/_/_/ _/_/_/ jcea@jcea.es - http://www.jcea.es/ _/_/ _/_/ _/_/ _/_/ _/_/ jabber / xmpp:jcea@jabber.org _/_/ _/_/ _/_/_/_/_/ . _/_/ _/_/ _/_/ _/_/ _/_/ "Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/ "My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/ "El amor es poner tu felicidad en la felicidad de otro" - Leibniz -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQCVAwUBTYwQYZlgi5GaxT1NAQI5pgP/btNjHZnGu1lFgoWLPOnQfK1fM9glufyZ YenlTJDlSXrieheam8SOUXMmNX/dgvjVxqfDvXmRFosoPIPZlEFDMTwPxyq99mVu MihH8UYFVy87+9xngL7IiWctKMwAQRHZcuOZayqKBWqA9lSDOSD2s9e27L1Xyypm xNpkX9lRIoo= =VaPC -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
PEP 0001 still lists SVN as the way to checkout/commit PEPs. I guess that place would be the right place to document the details about keywords & mercurial.
Jesus Cea Avion _/_/ _/_/_/ _/_/_/ jcea@jcea.es - http://www.jcea.es/ _/_/ _/_/ _/_/ _/_/ _/_/ jabber / xmpp:jcea@jabber.org _/_/ _/_/ _/_/_/_/_/ . _/_/ _/_/ _/_/ _/_/ _/_/ "Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/ "My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/ "El amor es poner tu felicidad en la felicidad de otro" - Leibniz -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQCVAwUBTYwmQZlgi5GaxT1NAQJwRwP/Wnc4iYzYn+eD4fQ1gzipbrZO5DTs54Aa iTugXjWCLN/jQ9EmJatRyMxcwT999dyY7r25vsFF17YvqH4CLbmHNbe2SxKmfQlO KZ9wm9pR1TAXBnNskT+MhvdJJ0rwSjPC25z6nPWhZky6zDl8AzB/JyqquBiVIX1S SK4dKh+EPIY= =bKsT -----END PGP SIGNATURE-----
Am 25.03.2011 04:47, schrieb Jesus Cea:
On 24/03/11 22:29, Georg Brandl wrote:
These requirements (activate the keyword extension, and set it to "**.txt" files) should be documented somewhere... :).
Well, I don't think it's required for anyone other than python.org. Those who edit the PEPs just need to keep the $Revision$ and $Date$ intact.
So, must I disable the extension KW again?. I am confused.
No. You may enable the extension, or you may disable it, just as you like. It makes no difference.
Maybe editors simply must keep "$Revision$" and "$Date$", since those keywords are expanded in the server, for showing in docs.python.org?.
Editors may add the keywords, or they may remove them, just as they like. It does make a difference and is the choice of the editor. In any case, the PEPs don't show up in docs.python.org (AFAIK), but in http://www.python.org/dev/peps/.
Regards, Martin
On Thu, Mar 24, 2011 at 6:41 AM, Georg Brandl <g.brandl@gmx.net> wrote:
Please commit any PEP changes to hg.python.org/peps.
Also, sorry for the span on -checkins, I should not have enabled the notification hook before pushing all changes :)
With the quick and easy svn:external reference to docutils gone, could we get the README updated with where to find docutils?
Cheers, Nick.
-- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia
On 26.03.2011 05:01, Nick Coghlan wrote:
On Thu, Mar 24, 2011 at 6:41 AM, Georg Brandl <g.brandl@gmx.net> wrote:
Please commit any PEP changes to hg.python.org/peps.
Also, sorry for the span on -checkins, I should not have enabled the notification hook before pushing all changes :)
With the quick and easy svn:external reference to docutils gone, could we get the README updated with where to find docutils?
I'd have thought that docutils is pretty much universally available nowadays. But you're right that README is out of date, I've updated it now.
Georg
On Sun, Mar 27, 2011 at 3:12 AM, Georg Brandl <g.brandl@gmx.net> wrote:
I'd have thought that docutils is pretty much universally available nowadays. But you're right that README is out of date, I've updated it now.
Yeah, it turned out to just be a "sudo apt-get python-docutils" away. I'm just unused to having to even think about it :)
Cheers, Nick.
-- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia
participants (5)
-
"Martin v. Löwis" -
Georg Brandl -
Jesus Cea -
Ned Deily -
Nick Coghlan