PyPI release schedule

[pyav-org]

PyPI release schedule

[mikeboers]

The bigger question is, "under what conditions do we feel it is safe to do so?".

I guess, since the version number does still start with a zero, that is whenever we feel like as an unplanned backwards incompatibility surplus is... not quite "ok", but allowable.

Do you want me to roll it together now?

[billyshambrook]

That would be great thanks! Just helps with packaging with other libraries.
Sent using CloudMagic
On Thu, Sep 11, 2014 at 11:03 pm, Mike Boers [email protected] wrote:The bigger question is, "under what conditions do we feel it is safe to do so?".

I guess, since the version number does still start with a zero, that it whenever we feel like as an unplanned backwards incompatibility surplus is... not quite "ok", but allowable.

Do you want me to roll it together now?

—Reply to this email directly or view it on GitHub.

[mikeboers]

v0.2.0 is on the PyPI. Hopefully I didn't just break everything. ;)

[simora]

i must have installed the latest from pypi... prior to your v0.2.0 release
but i can't import open from master or your remux branch.

from av import open
Traceback (most recent call last):
File "", line 1, in
File "av/init.py", line 4, in
from ._core import time_base
ImportError: av/_core.so: undefined symbol: avdevice_register_all

On Thu, Sep 11, 2014 at 6:46 PM, Mike Boers [email protected]
wrote:

Closed #49 #49.

—
Reply to this email directly or view it on GitHub
#49 (comment).

[mikeboers]

*flips the table*

Moving this to #50.