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

Python 3 Support in pScheduler #483

Open
arlake228 opened this issue Jun 16, 2017 · 3 comments
Open

Python 3 Support in pScheduler #483

arlake228 opened this issue Jun 16, 2017 · 3 comments
Assignees

Comments

@arlake228
Copy link
Collaborator

@arlake228 arlake228 commented Jun 16, 2017

See title. This is the way the world seems to be going so we will need to do this sometime in the not-so-distant future. Putting in Icebox for now, but don't want to forget about it.


Known TODOs:

  • Test Esmond archiver (Andy)
  • Test SNMP tests/tools/archiver (Ed)
  • Debian packaging (Antoine)

Known issues:

  • See why server isn't started after install (Mark)
  • See why scheduler runs slower (Mark)
  • Limit processor can't find library modules
  • See what happens when a tool enumerates a test that's not installed. (curl being the poster child).
@vvidic

This comment has been minimized.

Copy link
Collaborator

@vvidic vvidic commented Dec 7, 2017

Python 2.7 is supposed to be EOL 2020 and might not be included in the next Debian version. Python3 ships with a 2to3 tool to help with the conversion.

CentOS 7 does not ship python3 but epel contains python3.4. Supported libraries might also be a problem (only ~300 compared to 1500 for python2).

Default python 3 versions included in:

  • Debian 8: python 3.4
  • Debian 9: python 3.5
  • Debian next: python 3.6
  • Ubuntu 14: python 3.4
  • Ubuntu 16: python 3.5
  • Ubuntu next: python 3.6
@arlake228 arlake228 added the Epic label Aug 10, 2018
@arlake228 arlake228 removed the Epic label May 29, 2019
@arlake228 arlake228 changed the title Python 3 Support Python 3 Support in pScheduler May 29, 2019
@mfeit-internet2 mfeit-internet2 added Epic and removed Epic labels Jun 6, 2019
mfeit-internet2 added a commit that referenced this issue Aug 17, 2019
mfeit-internet2 added a commit that referenced this issue Aug 17, 2019
mfeit-internet2 added a commit that referenced this issue Aug 17, 2019
mfeit-internet2 added a commit that referenced this issue Aug 17, 2019
mfeit-internet2 added a commit that referenced this issue Aug 17, 2019
mfeit-internet2 added a commit that referenced this issue Aug 17, 2019
mfeit-internet2 added a commit that referenced this issue Aug 17, 2019
mfeit-internet2 added a commit that referenced this issue Aug 17, 2019
mfeit-internet2 added a commit that referenced this issue Aug 17, 2019
mfeit-internet2 added a commit that referenced this issue Aug 17, 2019
mfeit-internet2 added a commit that referenced this issue Aug 17, 2019
mfeit-internet2 added a commit that referenced this issue Aug 17, 2019
mfeit-internet2 added a commit that referenced this issue Aug 17, 2019
mfeit-internet2 added a commit that referenced this issue Aug 17, 2019
mfeit-internet2 added a commit that referenced this issue Aug 19, 2019
mfeit-internet2 added a commit that referenced this issue Sep 11, 2019
mfeit-internet2 added a commit that referenced this issue Sep 11, 2019
mfeit-internet2 added a commit that referenced this issue Sep 13, 2019
mfeit-internet2 added a commit that referenced this issue Sep 17, 2019
mfeit-internet2 added a commit that referenced this issue Sep 17, 2019
mfeit-internet2 added a commit that referenced this issue Sep 25, 2019
mfeit-internet2 added a commit that referenced this issue Sep 25, 2019
mfeit-internet2 added a commit that referenced this issue Jan 14, 2020
mfeit-internet2 added a commit that referenced this issue Jan 14, 2020
mfeit-internet2 added a commit that referenced this issue Jan 14, 2020
mfeit-internet2 added a commit that referenced this issue Jan 15, 2020
mfeit-internet2 added a commit that referenced this issue Jan 16, 2020
mfeit-internet2 added a commit that referenced this issue Jan 18, 2020
mfeit-internet2 added a commit that referenced this issue Jan 24, 2020
mfeit-internet2 added a commit that referenced this issue Jan 24, 2020
mfeit-internet2 added a commit that referenced this issue Jan 27, 2020
@tonin tonin self-assigned this Feb 13, 2020
@tonin

This comment has been minimized.

Copy link
Member

@tonin tonin commented Mar 25, 2020

I think we're still missing a few python -m compileall call replacements with the $(PYTHON) variable as we have in the pscheduler-server/api-server/Makefile I see that in most/all of the tests and tools and in the esmond-archiver.

mfeit-internet2 added a commit that referenced this issue Mar 30, 2020
@mfeit-internet2

This comment has been minimized.

Copy link
Member

@mfeit-internet2 mfeit-internet2 commented Mar 30, 2020

@tonin What you found has been fixed by cf8c1a5.

Change your build process so that any make doing python -m compileall passes PYTHON=xxx on the make command line as the RPM specs now do:

build
make \
     PYTHON=%{_pscheduler_python} \
     DESTDIR=$RPM_BUILD_ROOT/%{dest} \
     install
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants
You can’t perform that action at this time.