aboutsummaryrefslogtreecommitdiff
path: root/doc/todo
diff options
context:
space:
mode:
authorAmitai Schleier <schmonz-web-ikiwiki@schmonz.com>2018-01-08 08:15:53 -0500
committerAmitai Schleier <schmonz-web-ikiwiki@schmonz.com>2018-01-08 08:15:53 -0500
commit9ddb60e44b3db3dfa1c7a1e38be761689658cb7a (patch)
tree1c760a0f25170dcccc46ce195d442f518fae1818 /doc/todo
parenta147f5349d33b27b6eeac3279cba289c952ee835 (diff)
downloadikiwiki-9ddb60e44b3db3dfa1c7a1e38be761689658cb7a.tar
ikiwiki-9ddb60e44b3db3dfa1c7a1e38be761689658cb7a.tar.gz
co-maintainer opinion
Diffstat (limited to 'doc/todo')
-rw-r--r--doc/todo/consider_using_python3_for_rst_plugin.mdwn8
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/todo/consider_using_python3_for_rst_plugin.mdwn b/doc/todo/consider_using_python3_for_rst_plugin.mdwn
index 5135d153a..b95dff641 100644
--- a/doc/todo/consider_using_python3_for_rst_plugin.mdwn
+++ b/doc/todo/consider_using_python3_for_rst_plugin.mdwn
@@ -15,3 +15,11 @@ by changing the source rather than by using `sed` after installation. I didn't a
change upstream immediately to give other maintainers a chance to comment. Thoughts?
--[[smcv]]
+
+> I can attest as a pkgsrc developer, where we try to build and package
+> software on all sorts of platforms (some old and wacky), that as long
+> as the relevant Pythons build on those platforms (and we tend to make
+> sure they do), I don't foresee any negative impact of your suggested
+> change to ikiwiki. Can't attest for other situations, but am generally
+> biased toward biting future bullets as early as possible.
+> --[[schmonz]]