Downgrade ptyprocess

[shanemcd]

See pexpect/ptyprocess@8be4906#diff-522adf759addbd3b193c74ca85243f7d for more info

[shanemcd]

Also verified w/ OOB non-unit tests

[softwarefactory-project-zuul]

Build succeeded.

• awx-api-lint : SUCCESS in 8m 54s
• awx-ui-lint : SUCCESS in 9m 03s
• awx-api : SUCCESS in 12m 19s
• awx-ui : SUCCESS in 11m 13s
• awx-swagger : SUCCESS in 14m 32s
• awx-detect-schema-change : FAILURE in 13m 30s (non-voting)

[AlanCoding]

It would be good to add to the note that this is only necessary for python2 virtual environments. I tried to look into an alternative where we add an entry of ptyprocess==0.5.2; python_version < '3' to the requirements.in file. Doing that, I found this in the py2 vs py3 requirements:

87c91
< ptyprocess==0.6.0         # via pexpect
---
> ptyprocess==0.5.2 ; python_version < "3"

So it would be automatically added as a conditional requirement for the python2 reqs, but would be added as most recent to the python3 reqs. These need to be manually re-combined in the (still combined) Ansible venv requirements file. That would be possible, but doesn't follow the same pattern as our other manual steps.

Since an upstream fix may be coming sometime soon, I agree with avoiding that work for pinning it for both py2 and py3 until upstream fixes it.

[ryanpetrello]

@shanemcd once this gets fixed upstream (sounds like it's happening soon), let's just remove this pin.

[softwarefactory-project-zuul]

Build succeeded (gate pipeline).

• awx-api-lint : SUCCESS in 3m 39s
• awx-ui-lint : SUCCESS in 3m 16s
• awx-api : SUCCESS in 7m 36s
• awx-ui : SUCCESS in 4m 43s
• awx-swagger : SUCCESS in 7m 22s
• awx-detect-schema-change : FAILURE in 8m 06s (non-voting)
• awx-push-new-schema : SUCCESS in 6m 41s (non-voting)