<html><body><div style="font-family: times new roman, new york, times, serif; font-size: 12pt; color: #000000"><hr id="zwchr"><blockquote style="border-left:2px solid #1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><div class="gmail_quote">Pete Travis <<a href="mailto:me@petetravis.com" target="_blank">me@petetravis.com</a>> schrieb am Mon Jan 26 2015 at 5:24:32 PM:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 01/26/2015 08:53 AM, Zbigniew Jędrzejewski-Szmek wrote:<br>
> Hi,<br>
><br>
> since bug #1126521 seems to be progressing nicely, I think it would be<br>
> nice to get in touch with python-sig, the maintainers of<br>
> python3-dateutil, about retiring python3-dateutil and adding a python3<br>
> subpackage to python-dateutil. They might want to do it the other way<br>
> around, which would be fine too, but either way, something should be<br>
> arranged.<br>
><br>
> I tried to sign up for the python-sig mailing list, but it is<br>
> "private" and I haven't received any welcome letter, so I think I'm<br>
> stuck in some moderation queue.<br>
><br>
> Zbyszek<br>
<br>
Yes, I think it's a good time to bring up retiring python3-dateutil.<br>
I've also requested membership for that list, and included the list<br>
owners here, maybe they can expedite our requests.<br></blockquote><div><br></div><div>As python-dateutil is not (yet) under the python-sig group maintainership [1], you could reach the maintainers of python-dateutil under ther -owner mail address (CC'ed).</div><div>python-sig@fp.o is for all group maintained package maintainers and general python related questions are handled on python-devel@fp.o (also CC'ed). (Sorry for the confusion, the python-sig groupmaintainership started very recently and is still a work in process.)</div><div><br></div><div>I'd say it depends, how python3 will be introduced in F22, which package should provide the subpackage and the other one should be retired.</div><div>Maybe someone from [2] could comment on what they like to see in the future. I don't mind having two separate packages until we approach F22 and the future process is here.</div><div><br></div><div>Greetings,</div><div> Tom</div><div><br></div><div>[1] <a href="https://admin.fedoraproject.org/pkgdb/package/python-dateutil/" target="_blank">https://admin.fedoraproject.org/pkgdb/package/python-dateutil/</a><br data-mce-bogus="1"></div><div>[2] <a href="http://fedoraproject.org/wiki/Changes/Python_3_as_Default" target="_blank">http://fedoraproject.org/wiki/Changes/Python_3_as_Default</a><br data-mce-bogus="1"></div></div></blockquote><div><br></div><div>Packaging Python extension modules should keep working the way it did up until F21. python-dateutil will still be the Python2 build, python3-datetuil will still be the Python3 build. There are some guidelines changes that I proposed for F22 [1], but I think they don't influence dateutil.<br></div><div><br></div><div>Slavek<br></div><div><br></div><div>[1] https://fedorahosted.org/fpc/ticket/475#comment:5<br></div></div></body></html>