-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 14.09.2010 22:42, schrieb Dougn: > Man this was a hard one to track down. > Some of my object.inv files were not being loaded due to some odd zlib > error. This is on windows, python 2.6.1. > > The problem? While the inventory file is being written in binary mode > for v2, it is being read in text mode in intersphinx. > Why is that an issue? Well it means that if the compressed stream > contains mungable characters (like \r\n or the special windows EOF > character) the data will be modified. And that is what is happening. > In my case it is finding the special EOF character that windows, in > its infinite wisdom and desire to have viruses, decided to implement > and keep around. > > So I get a truncated inventory file on read. > > The file is written in binary mode, and the '\n' is explicit so there > should not be OS line termination issues for version 2 of teh file, > but there will be for version 1. *sigh* > > Bug is listed here: > > http://bitbucket.org/birkenfeld/sphinx/issue/524/intersphinx-corrupt-objectsinv-due-to-zlib-issue-on
This bug is now fixed in 1.0.4, released just now. Georg -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iEYEARECAAYFAkyTIkAACgkQN9GcIYhpnLA7EgCfTc1x4oQ8dLbQyJ3fd8LVcTAn 53AAoKR7xSPB4OQNtYOSQHtuRIHLIQJ2 =Y8Yq -----END PGP SIGNATURE----- -- You received this message because you are subscribed to the Google Groups "sphinx-dev" group. To post to this group, send email to sphinx-...@googlegroups.com. To unsubscribe from this group, send email to sphinx-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sphinx-dev?hl=en.
