Remove six python2->3 compatibility helper usage

[davidlange6]

(breaks python2 compatibility) - done mostly via script, lets see what mistakes my script made..

[cmsbuild]

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-34534/24046

• This PR adds an extra 1004KB to repository

• There are other open Pull requests which might conflict with changes you have proposed:

  • File Configuration/AlCa/python/autoCondPhase2.py modified in PR(s): Run 2, Run3, and Phase2 tracker: adding T27 (geometry with bricked pixels) and support for storing bricked pixel information #34120
  • File Configuration/Applications/python/ConfigBuilder.py modified in PR(s): Fix when neither "data" nor "MC" is specified in the cmsDriver. #34452
  • File Configuration/PyReleaseValidation/python/upgradeWorkflowComponents.py modified in PR(s): Run 2, Run3, and Phase2 tracker: adding T27 (geometry with bricked pixels) and support for storing bricked pixel information #34120, Add run3 tracking low pu era #33532, [DD4hep] Enable Run 3 DD4hep DB workflow with correct GT for PR & IB tests #34526, Bianca pinolini ecal reco phase2 commit unimib #34212
  • File FWCore/ParameterSet/scripts/edmConfigSplit modified in PR(s): Used importlib in scripts #34490
  • File HeterogeneousCore/SonicTriton/test/tritonTest_cfg.py modified in PR(s): SonicTriton feature updates, improvements, bug fixes #34508
  • File PhysicsTools/NanoAOD/test/inspectNanoFile.py modified in PR(s): DRAFT: nano: adaptation to run in Prompt #34329
  • File RecoLuminosity/LumiDB/scripts/pileupCalc.py modified in PR(s): Use numpy and scipy to speed up pileupCalc.py #34092
  • File Validation/Geometry/test/MaterialBudget.py modified in PR(s): python2 cleanup: Validation packages #34427
  • File Validation/RecoB/scripts/cuy.py modified in PR(s): python2 cleanup: Validation packages #34427
  • File Validation/RecoTau/python/ValidationOptions_cff.py modified in PR(s): python2 cleanup: Validation packages #34427
  • File Validation/RecoTau/python/compare.py modified in PR(s): python2 cleanup: Validation packages #34427
  • File Validation/RecoTrack/python/TrackValidation_cff.py modified in PR(s): EXO regional tracking iteration #32806
  • File Validation/RecoTrack/python/plotting/html.py modified in PR(s): EXO regional tracking iteration #32806
  • File Validation/RecoTrack/python/plotting/ntupleEnum.py modified in PR(s): EXO regional tracking iteration #32806
  • File Validation/RecoTrack/python/plotting/trackingPlots.py modified in PR(s): EXO regional tracking iteration #32806
  • File Validation/RecoTrack/test/fakeAnalysis/analysis.py modified in PR(s): python2 cleanup: Validation packages #34427
  • File Validation/Tools/python/GenObject.py modified in PR(s): python2 cleanup: Validation packages #34427

[cmsbuild]

A new Pull Request was created by @davidlange6 (David Lange) for master.

It involves the following packages:

• Alignment/HIPAlignmentAlgorithm (alca)
• Alignment/MillePedeAlignmentAlgorithm (alca)
• Alignment/OfflineValidation (alca)
• CalibTracker/SiStripDCS (alca)
• CalibTracker/SiStripESProducers (alca)
• CommonTools/ParticleFlow (reconstruction)
• CondCore/ESSources (db, alca)
• CondTools/BTau (db)
• CondTools/SiStrip (db)
• Configuration/AlCa (alca)
• Configuration/Applications (operations)
• Configuration/HLT (hlt)
• Configuration/PyReleaseValidation (pdmv, upgrade)
• Configuration/StandardSequences (operations)
• DQM/Integration (dqm)
• DQM/SiStripMonitorClient (dqm)
• DQM/TrackerRemapper (dqm)
• DQM/TrackingMonitorSource (dqm)
• DQMOffline/Configuration (dqm)
• DQMOffline/L1Trigger (dqm, l1)
• FWCore/Concurrency (core)
• FWCore/Modules (core)
• FWCore/ParameterSet (core)
• FWCore/PythonUtilities (core)
• FWCore/Services (core)
• FWCore/Utilities (core)
• FastSimulation/TrackingRecHitProducer (fastsim)
• HLTrigger/Configuration (hlt)
• HLTrigger/HLTanalyzers (hlt)
• HLTrigger/Tools (hlt)
• HLTriggerOffline/Egamma (dqm)
• HeterogeneousCore/SonicTriton (heterogeneous)
• L1Trigger/Configuration (l1)
• L1Trigger/L1TCalorimeter (l1)
• L1Trigger/L1TMuonEndCap (l1)
• L1TriggerConfig/Utilities (l1)
• PhysicsTools/Heppy (analysis)
• PhysicsTools/HeppyCore (analysis)
• PhysicsTools/NanoAOD (xpog)
• PhysicsTools/PatAlgos (reconstruction)
• PhysicsTools/PythonAnalysis (analysis)
• PhysicsTools/Utilities (analysis)
• RecoBTag/ONNXRuntime (reconstruction)
• RecoLuminosity/LumiDB (db)
• RecoTauTag/Configuration (reconstruction)
• RecoTauTag/RecoTau (reconstruction)
• RecoTracker/Configuration (reconstruction)
• RecoVertex/BeamSpotProducer (reconstruction, alca)
• SimG4CMS/HGCalTestBeam (upgrade, simulation)
• TauAnalysis/MCEmbeddingTools (simulation)
• Utilities/RelMon (dqm)
• Utilities/ReleaseScripts (core)
• Validation/Configuration (dqm, simulation)
• Validation/Geometry (geometry, dqm)
• Validation/HGCalValidation (dqm)
• Validation/RecoB (dqm)
• Validation/RecoTau (dqm)
• Validation/RecoTrack (dqm)
• Validation/Tools (core)

@andrius-k, @gouskos, @lveldere, @chayanit, @bbilin, @wajidalikhan, @sbein, @ianna, @kpedro88, @Martin-Grunewald, @rekovic, @tlampen, @jpata, @pohsun, @santocch, @cecilecaillol, @perrotta, @civanch, @yuanchao, @makortel, @ErnestaP, @ahmad3213, @cmsbuild, @fwyzard, @davidlange6, @smuzaffar, @Dr15Jones, @cvuosalo, @mdhildreth, @jfernan2, @kskovpen, @slava77, @ggovi, @qliphy, @fabiocos, @francescobrivio, @malbouis, @ssekmen, @jordan-martins, @kmaeshima, @silviodonato, @srimanob, @fgolf, @mariadalfonso, @tvami, @rvenditti can you please review it and eventually sign? Thanks.
@wmtford, @echabert, @rappoccio, @gouskos, @hdelanno, @felicepantaleo, @jandrea, @robervalwalsh, @emilbols, @kpedro88, @gbenelli, @Martin-Grunewald, @bsunanda, @pfs, @thomreis, @tlampen, @mbluj, @rishabhCMS, @threus, @mmusich, @seemasharmafnal, @venturia, @mmarionncern, @sethzenz, @apsallid, @makortel, @JanFSchulte, @dgulhan, @missirol, @JyothsnaKomaragiri, @slomeo, @sroychow, @jdamgov, @lgray, @mariadalfonso, @vandreev11, @pieterdavid, @cvuosalo, @GiacomoSguazzoni, @tocheng, @VinInn, @cseez, @gpetruc, @nhanvtran, @gkasieczka, @rovere, @schoef, @idebruyn, @ebrondol, @mtosi, @fabiocos, @clelange, @rbartek, @arossi83, @batinkov, @swertz, @adewit, @riga, @battibass, @swozniewski, @wddgit, @jdolen, @ahinzmann, @hatakeyamak, @vargasa, @lecriste, @cbernet, @dinyar, @matt-komm, @andrzejnovak, @rociovilar, @fioriNTU this is something you requested to watch as well.
@silviodonato, @dpiparo, @qliphy, @perrotta you are the release manager for this.

cms-bot commands are listed here

[Martin-Grunewald]

+1

[Martin-Grunewald]

@smuzaffar
I can't get the script to work making a developer area with this this PR as advertised above:

/cvmfs/cms-ci.cern.ch/week0/cms-sw/cmssw/34534/17027/install.sh
++ /bin/pwd
+ XDIR=/data/CMS0/test
+ export SCRAM_ARCH=slc7_amd64_gcc900
+ SCRAM_ARCH=slc7_amd64_gcc900
+ '[' -e CMSSW_12_0_X_2021-07-20-1100 ']'
+ tar -xzf /cvmfs/cms-ci.cern.ch/week0/cms-sw/cmssw/34534/17027/cmssw.tar.gz
+ cd CMSSW_12_0_X_2021-07-20-1100
++ cat config/scram_version
+ SCRAM_VER=V3_00_30
+ EXT=pl
+ SCRAM_HOME_BASE=src
++ echo V3_00_30
++ grep '^V3'
++ wc -l
+ '[' 1 -gt 0 ']'
+ EXT=py
+ SCRAM_HOME_BASE=
+ export SCRAM_TOOL_HOME=/cvmfs/cms-ib.cern.ch/week0/share/lcg/SCRAMV1/V3_00_30/
+ SCRAM_TOOL_HOME=/cvmfs/cms-ib.cern.ch/week0/share/lcg/SCRAMV1/V3_00_30/
+ ./config/SCRAM/projectAreaRename.py /data/cmsbld/jenkins/workspace/ib-run-pr-tests /data/CMS0/test slc7_amd64_gcc900
'utf-8' codec can't decode byte 0x84 in position 8: invalid start byte Error: Unable to read file /data/CMS0/test/CMSSW_12_0_X_2021-07-20-1100/config/SCRAM/Plugins/CMSSW/__pycache__/ExtraBuildRule.cpython-38.pyc
'utf-8' codec can't decode byte 0x84 in position 8: invalid start byte Error: Unable to read file /data/CMS0/test/CMSSW_12_0_X_2021-07-20-1100/config/SCRAM/Plugins/__pycache__/BuildRules.cpython-38.pyc
+ ./config/SCRAM/linkexternal.py --arch slc7_amd64_gcc900
+ find config/SCRAM -name __pycache__ -type d
+ xargs --no-run-if-empty rm -rf

My default shell is tcsh, but same error if I switch to sh

[cecilecaillol]

+l1

[smuzaffar]

what type of error you get @Martin-Grunewald ? For me it works on lxplus. /cvmfs/cms-ci.cern.ch/week0/cms-sw/cmssw/34534/17027/install.sh creates local CMSSW_12_0_X_2021-07-20-1100 directory and I can go in there, setup env (cmsenv) and use the area.

[Martin-Grunewald]

See above the output of the scripts, esp the two utf8 errors:

'utf-8' codec can't decode byte 0x84 in position 8: invalid start byte Error: Unable to read file /data/CMS0/test/CMSSW_12_0_X_2021-07-20-1100/config/SCRAM/Plugins/CMSSW/__pycache__/ExtraBuildRule.cpython-38.pyc
'utf-8' codec can't decode byte 0x84 in position 8: invalid start byte Error: Unable to read file /data/CMS0/test/CMSSW_12_0_X_2021-07-20-1100/config/SCRAM/Plugins/__pycache__/BuildRules.cpython-38.pyc

and if I then try to add another PR, I get this error:

git cms-merge-topic 34563
From .
 * [new ref]                            -> merge-attempt
From https://github.com/cms-sw/cmssw
 * [new ref]                 refs/pull/34563/head -> cms-sw/refs/pull/34563/head
Switched to branch 'merge-attempt'
fatal: unable to read tree 48bba69e8b701357dac0b29ecf33807d78524848

[smuzaffar]

please ignore the 'utf-8' codec can't decode byte 0x84 type messages. The area is build and populated with PR #34534 contents. I do not think that you can run another git cms-merge-topic ... there. This area is provided so that you can re-run the tests to debug. What do you want to achieve? If you just want to test #34563 with #34534 then why not start PR test for #34563 with extra PR #34534?

[Martin-Grunewald]

OK, thanks for the clarification!

[ggovi]

+1

[silviodonato]

merge

[santocch]

+1