Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[py2py3] Migration at level scr/python/A/B/C - slice 2 #10098

Closed
mapellidario opened this issue Nov 23, 2020 · 0 comments · Fixed by #10103
Closed

[py2py3] Migration at level scr/python/A/B/C - slice 2 #10098

mapellidario opened this issue Nov 23, 2020 · 0 comments · Fixed by #10103
Assignees
Labels
New Feature py2py3 slice Issue related to slicing the modernization to py2py3 Python3

Comments

@mapellidario
Copy link
Member

mapellidario commented Nov 23, 2020

Intro

Our purpose is to continue with the gradual migration. This is the second slice in which the migration has been divided into. We have split migration units at level src/python/A/B/C.

A detailed plan of the migration at this depth is available at the dmwm mkdocs detailed plan page, with summary information on top.

Impact of the new feature

We start migrating the second bulk of migration units at src/python/A/B/C level, which will include:

                                 name  #files  gradual  changes (+ and -)
          WMCore_ACDC_CollectionTypes       1     True          0
           WMCore_Agent_DefaultConfig       1     True          0
                 WMCore_Configuration       1     True         13
             WMCore_Database_Dialects       1     True          0
          WMCore_GroupUser_Decorators       1     True          0
                        WMCore_ReqMgr       2     True          0
                WMCore_Services_HTTPS       1     True         16
              WMCore_WMSpec_Utilities       1     True          0
 WMCore_WorkQueue_WorkQueueExceptions       1     True          0
         WMCore_FwkJobReport_FileInfo       1     True          2
            WMCore_MicroService_Tools       1     True          5
                WMCore_Services_Rucio       1     True         14
         WMCore_WebTools_FrontEndAuth       1     True          2
               WMCore_ACDC_Collection       1     True          0
                  WMCore_ACDC_Fileset       1     True          0
        WMQuality_Emulators_ReqMgrAux       1     True          1
             WMCore_Agent_ConfigDBMap       1     True          0
    WMCore_Storage_TrivialFileCatalog       1     True          7
      WMCore_WMSpec_ConfigSectionTree       1     True          6
        WMCore_WebTools_DefaultConfig       1     True          0
    WMQuality_Emulators_DefaultConfig       1     True          0
    WMQuality_Emulators_EmulatorSetup       1     True          0
                    WMCore_DAOFactory       1     True          3
          WMCore_Database_Transaction       1     True          0
  WMCore_JobSplitting_SplitterFactory       1     True          0
                 WMCore_WebTools_Page       1     True          3
            WMCore_Database_DBCreator       1     True          9
         WMCore_ResourceControl_MySQL      13     True          6
              WMCore_ThreadPool_MySQL       3     True          0
           WMCore_WMBS_CreateWMBSBase       1     True          2
               WMQuality_TestDB_MySQL       2     True          0
        WMCore_ResourceControl_Oracle      13     True          0
                WMCore_Database_MySQL       2     True          0
               WMCore_Database_Oracle       2     True          0
              WMQuality_TestDB_Oracle       3     True          0
        WMCore_ThreadPool_ThreadSlave       1     True          8

Is your feature request related to a problem? Please describe.

The end goal is to have WMCore py2 and py3 compatible.

Describe the solution you'd like

Run futurize on the first bulk of units and then apply the necessary manual changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
New Feature py2py3 slice Issue related to slicing the modernization to py2py3 Python3
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant