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

Backward compatibility with Python 2.4-3.4 (server) #56

Closed
wants to merge 4 commits into from

Conversation

vieira
Copy link
Contributor

@vieira vieira commented Jan 7, 2016

It is often the case that the user has no administrative control over
the server that is being used. As such it is important to support as
many versions as possible, at least on the remote server end. These
fixes will allow sshuttle to be used with servers that have only
python 2.4 or python 2.6 installed while hopefully not breaking the
compatibility with 2.7 and 3.5.

I have tested this set of fixes on the following python versions (server):

  • 2.4.6
  • 2.5.6
  • 2.6.9
  • 2.7.3
  • 3.1.5
  • 3.2.3
  • 3.3.6
  • 3.4.3
  • 3.5.0

It is often the case that the user has no administrative control over
the server that is being used. As such it is important to support as
many versions as possible, at least on the remote server end. These
fixes will allow sshuttle to be used with servers that have only
python 2.4 or python 2.6 installed while hopefully not breaking the
compatibility with 2.7 and 3.5.
These changes will allow sshuttle to be used with servers that
have python 3.4 installed (e.g. CentOS 7, Debian 8, Ubuntu 14.04).
Ported fixes from sshuttle#55 so they are compatible with older python versions.
brianmay added a commit that referenced this pull request Mar 16, 2016
This allows disabling all client tests using a conftest.py file, if for
example #56 gets merged and the server supports more python versions
then the server.

The server side tests are very incomplete.
@brianmay
Copy link
Member

Closing this in favour of #81.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants