ansible/bin
Toshio Kuratomi 84a59e472b Be explicit about pickle protocol and encoding (#24454)
On Python3 and Python2 use pickle slightly differently so we need to be
explicit about some things.

If pickles could be shared between python2 and python3, as in
ansible-connection and the pickle cache, we need to specify the protocol
to use when dumping and the encoding to use for byte strings when
loading.

The dumping protocol needs to be no higher than 2 as python-2 only
supports up to protocol 2.  The encoding should usually be 'bytes' so
that python2 str type becomes python3 bytes type.  However, doing this
means that we must make sure that the objects being serialized properly
make their strings into text strings except when they're supposed to be
bytes.  If strings are improperly byte strings, they may cause
tracebacks on the receiving end
2017-05-12 18:04:48 -07:00
..
ansible Handle downstream version additions (#22428) 2017-03-10 12:01:11 -08:00
ansible-connection Be explicit about pickle protocol and encoding (#24454) 2017-05-12 18:04:48 -07:00
ansible-console draft 1st release of ansible-console 2016-03-07 20:25:21 -05:00
ansible-doc Making the switch to v2 2015-05-03 21:47:26 -05:00
ansible-galaxy Making the switch to v2 2015-05-03 21:47:26 -05:00
ansible-playbook Making the switch to v2 2015-05-03 21:47:26 -05:00
ansible-pull Making the switch to v2 2015-05-03 21:47:26 -05:00
ansible-vault Making the switch to v2 2015-05-03 21:47:26 -05:00