From Fedora Project Wiki
(Created page with "{{admon/important | Comments and Explanations | The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To re...")
 
No edit summary
Line 1: Line 1:
{{admon/important | Comments and Explanations | The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "edit" link.<br/> '''Copy the source to a ''new page'' before making changes!  DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.'''}}
<!-- Self Contained or System Wide Change Proposal?
Use this guide to determine to which category your proposed change belongs to.
Self Contained Changes are:
* changes to isolated/leaf package without the impact on other packages/rest of the distribution
* limited scope changes without the impact on other packages/rest of the distribution
* coordinated effort within SIG with limited impact outside SIG functional area, accepted by the SIG
System Wide Changes are:
* changes that does not fit Self Contained Changes category touching
* changes that require coordination within the distribution (for example mass rebuilds, release engineering or other teams effort etc.)
* changing system defaults
For Self Contained Changes, sections marked as "REQUIRED FOR SYSTEM WIDE CHANGES" are OPTIONAL but FESCo/Wrangler can request more details (especially in case the change proposal category is
improper or updated to System Wide category). For System Wide Changes all fields on this form are required for FESCo acceptance (when applies). 
We request that you maintain the same order of sections so that all of the change proposal pages are uniform.
-->
<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name.  This keeps all change proposals in the same namespace -->
<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name.  This keeps all change proposals in the same namespace -->
= python-dateutil 2.x =
= python-dateutil 2.x =


Revision as of 15:13, 19 January 2015

python-dateutil 2.x

Summary

The package providing dateutil python libraries is currently on version 1.5. Early releases in the 2.x series of python-dateutil would work only for python3, so the package was not updated in Fedora. Now, python-dateutil is at version 2.4 and does work with python2. Fedora packages can be updated to use the newer version.

Owner

  • Name: Pete Travis
  • Email: immanetize AT fedoraproject.org
  • Release notes owner:

Current status

  • Targeted release: Fedora 222
  • Last updated: (DATE)
  • Tracker bug: <will be assigned by the Wrangler>

Detailed Description

Many newer python packages require the newer version of python-dateutil, but some still need python-dateutil 1.5 to function properly. Maintainers will assess affected packages, and can use the parallel installable python-dateutil15 package, which already exists in the distribution, if they cannot migrate.

Benefit to Fedora

Fedora can offer newer dateutil libraries, and newer packages that depend on dateutil.

Scope

  • Proposal owners:

Coordinate update efforts and assist maintainers in assessing, testing, and updating their packages.

  • Other developers:

Maintainers of packages that depend on python-dateutils should test with version 2.4, or the current release at freeze. If their package is not compatible with this version, they should change the packages Requires: to use python-dateutil15 and ensure that it works with the parallel-installable egg that it provides.

  • Release engineering: As each package should be assessed individually, a mass rebuild is not appropriate and release engineering has no requirements for this change.

Upgrade/compatibility impact

Existing functionality can be supported by the backwards compatibility package, but it is expected that most packages will be compatible with the newer version.

Post-F22, the compatibility package may be retired.

How To Test

Some ideas:

  • Use the package with newer python-dateutil and see if it breaks :)
  • Review code that uses python-dateutil modules for incompatible changes.

User Experience

Third party developers may need to review their work for compatibility, and use the appropriate package. End users of packages that depend on python-dateutils should not be impacted.

Dependencies

  • barman
  • bugwarrior
  • buildbot-master
  • calibre
  • condor-plumage
  • dmlite-shell
  • fedocal
  • freeipa-python
  • gtg
  • libopensync-plugin-moto
  • nagios-plugins-lcgdm-common
  • openerp
  • openerp7
  • openerp-client
  • pyqtrailer
  • python-arrow
  • python-bloom
  • python-botocore
  • python-bugzilla2fedmsg
  • python-catkin_pkg
  • python-collada
  • python-croniter
  • python-django-horizon
  • python-django-tastypie
  • python-fedmsg-meta-fedora-infrastructure
  • python-freezegun
  • python-gertty
  • python-icalendar
  • python-matplotlib
  • python-mwlib
  • python-nikola-extras
  • python-OWSLib
  • python-pandas
  • python-proteus
  • python-pypump
  • python-rhsm
  • python-tahrir
  • python-tahrir-api
  • python-taskw
  • python-tgscheduler
  • python-vcstools
  • python-vobject
  • python-wstool
  • pytrailer
  • ReviewBoard
  • s3cmd
  • subscription-manager
  • sugar-toolkit
  • sugar-toolkit-gtk3
  • supybot
  • tryton
  • trytond
  • TurboGears
  • vertica-python
  • wuja
  • yokadi
  • yum-plugin-changelog

Contingency Plan

  • Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
  • Contingency deadline: N/A (not a System Wide Change)
  • Blocks release? N/A (not a System Wide Change), Yes/No
  • Blocks product? product

Documentation

N/A (not a System Wide Change)

Release Notes

python-dateutil has been updated to version 2.4, allowing new versions of popular software in Fedora.

Retrieved from "https://fedoraproject.org/w/index.php?title=Changes/python-dateutil_2.x&oldid=401225"