Solve issue #2482

[vlsd]

First commit changes the order of arguments in the call to ffmpeg. Now output options go with the output file instead of the input file. This avoids an issue with ffmpeg 2.x rejecting the call.

Second commit fixes a bug where xrange() was assumed (incorrectly) to be a generator. It is in fact some sort of lazy list, so it does not have the __next__() method generators have.The bug manifested itself when calling FuncAnimate() with a constant number of frames, like in examples/animation/basic_example.py.

Third commit adds a note in the INSTALL document about the incompatibility of the tight setting for bbox with generating movies using pipe writers, like ffmpeg.

[tacaswell]

You might want to squash some of these commits.

[vlsd]

Sorry I just falsely assumed github would create a patch upon pull
requests. Silly me.
On Oct 3, 2013 4:53 PM, "Thomas A Caswell" notifications@github.com wrote:

You might want to squash some of these commits.

—
Reply to this email directly or view it on GitHubhttps://github.com//pull/2493#issuecomment-25661536
.

[tacaswell]

silly formatting thing, can you put the sentence about the incompatibility on a new line?

[vlsd]

done. let me know if that's not what you meant

[tacaswell]

@mdboom or @efiring Can you take a look at this one? I think it is ready to go, but am wary of the merge from master in the history.

[efiring]

@tacaswell, I think it needs to be rebased interactively to eliminate the merge commit. I would not merge it as-is.

[mdboom]

I have no issues with the content -- but as @efiring said, we'll need to get the merge commit out.

[vlsd]

Probably easiest if I just open a separate pull request on a new branch. Sorry for the mess.

[vlsd]

Moved all changes to a new branch and sent Pull Request #2615