Hello,
a last remark/discussion. Given that the XS-Python-Version field is no
more required, I think it shouldn't be mentionned as part of the official
policy but only as example on how to implement the policy with the help of
python-central.
I will update the wiki page as soon as the updated
* Raphael Hertzog ([EMAIL PROTECTED]) [060619 19:31]:
a last remark/discussion. Given that the XS-Python-Version field is no
more required, I think it shouldn't be mentionned as part of the official
policy but only as example on how to implement the policy with the help of
python-central.
I
Hi Andy,
On Mon, 19 Jun 2006, Andreas Barth wrote:
We shouldn't have two vastly different ways to do it.
Life would be best if we had already taken a decision... we know this but it is
not going to happen until we have more experience with both python-central and
python-support.
Either,
* Raphael Hertzog ([EMAIL PROTECTED]) [060619 21:08]:
On Mon, 19 Jun 2006, Andreas Barth wrote:
We shouldn't have two vastly different ways to do it.
Life would be best if we had already taken a decision... we know this but it
is
not going to happen until we have more experience with both
On Mon, 19 Jun 2006, Floris Bruynooghe wrote:
On Mon, Jun 19, 2006 at 09:07:00PM +0200, Raphael Hertzog wrote:
BTW, the syntax of the Python-Version field comes directly from
python-central and it has not been discussed if the current syntax is the
best needed to achieve the second point.
On Mon, 19 Jun 2006, Andreas Barth wrote:
My impression was that we *did* a decision how to handle the
meta-information, and just didn't decide about the implementation.
You can review the video of the BoF but I don't have time for that.
common denominator that I have found on which both
6 matches
Mail list logo
