>>>>> "TK" == Toshio Kuratomi <a.bad...@gmail.com> writes:
TK> However, you should check with tibbs/FPC about TK> whether the definitions/list of macros are an altogether dated TK> concept. I think it's reasonable to document macros which are going to need to use. Python packaging just isn't sufficiently regularized (or simple) that people can avoid having to come into more "intimate" contact with the macros. That documentation doesn't really have to be in the guidelines page, of course, and we could certainly move them out to a separate document. (We recommend but don't document %autosetup, for example. There's plenty of stuff you have to search for, which is unfortunate.) Currently we have them in a list that's collapsed by default so at least they don't take up too much space on the page. Note also that the guidelines are in the wiki for convenience, but there have been at least two efforts to move them to a "better" format. And I would truly love to have a companion set of documents which aren't guidelines but which expand on them and document things like this. Whether that ends up being maintained as part of the guidelines or separately hasn't even been discussed yet, but at least you'll be able to send a PR in pagure to get something updated. - J< _______________________________________________ python-devel mailing list -- python-devel@lists.fedoraproject.org To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org
