* Build additional "streamlinkw" launcher on Windows
1/2: Windows installer (using a pre-release version of pynsist)
* Build additional "streamlinkw" launcher on Windows
2/2: Windows specific wheels
* plugins.oldlivestream: remove plugin, service not available anymore
The old subdomain redirects to the new domain,
which is already a Streamlink plugin.
* plugins.oldlivestream: Add filename for empty files on Windows.
Python = 3.6.6
Pycryptodome = 3.6.4
Known Issue:
Old Python 3.5 files from a previous installation, won't be removed.
(because of the limitations of pynsist)
This changes the release date that is automatically added to the release
notes from your local timezone to UTC. If different people are deploying
two releases in different timezones, it is possible that a newer version
could be released "before" the previous version. For example, if someone
in Italy deployed a release at 01:00 2018-06-02 (UTC+2) and later
someone in California deployed a release at 22:00 2018-04-01 (UTC-7)- we
have a time travelling release. If all releases are labeled using UTC
then they will be consistent, however it is possible to have a "future"
release if you live west of the prime meridian.
* docs: build latest and stable docs with doctr
* docs: first attempt add enabling version switching with a warning
* build: remove {make,push}docs.sh scripts as they are no longer needed
* docs: moved doctr deploy key decryption key to travis settings
* docs: fix typo in css
* Move docs version selection to sidebar
Also:
- Remove home icon from "Streamlink" title
- Fix spacing and text layout in sidebar header and menu
- Remove border from active main menu list item
- Rename CSS classes (wy-side-nav-search -> wy-side-nav-header)
- Remove some unneeded CSS rules
* build: fix for universal wheel on python 2.7
* release: fix build order for deploys
The script to build the sdist and wheel packages is run before the
script that uploads them to PyPI. The sdist script doesn't clean up
the environment, but extra prune options have been added to the
MANIFEST.in file (thanks @back-to).
* build: ensure twine/wheel up-to-date and upload sdist/whl separately
Made the release script a bit more streamline. The only function it
really performs now is to update the changelog file and prepare a
release branch.
The script accepts some command line options:
--upstream REPO - the upstream repo (streamlink/streamlink)
--origin REPO - the users fork of the repo
--version VERSION - the new version number
The script will work out the current version and generate a git shortlog
and update the changelog file, then launch the users $EDITOR so that it
can be updated ($VISUAL, or $EDITOR, then fallback to vi).
* deploy: automatically deploy sdist and wheel builds to PyPI.
* build: limit deploys to streamlink repo
* build: remove pypi methods from release script
* build: build and sign sdist in travis using an RSA sign-only key
* build: combine the build and sign with pypi deploy
* rename CHANGELOG to md
* symlink the change log in to the docs
* include the recommonmark parser for md file
* reformatted the CHANGELOG md file, should look more or less the same as the RST
* refactored the release scripts to handle/generate the new format
* file is a bad variable name
* couple of minor tweaks, mainly style
* Fix git shortlog being highlighted as Python in the docs
* update manifest to include changelog.md instead of rst
* build: use versioneer to set the build number
* build: update the deploy scripts to use versioneer
* release: update docs version and fix tarball version
* build: no need to install versioneer on travis, etc.
Any proxy type that is supported by `requests` can be used.
For example, SOCKS proxies are support by `requests`, and can be used:
- `--http-proxy "socks5://[user:password@]host:port"`
- `--https-proxy "socks5://[user:password@]host:port"`
to set streamlink to use socks proxies for http and https.
`pkg_resources` (`setuptool`) and `requests` have changed the way their
packages are structured so that they no longer vendor packages, this
means those previously vendored packages have to be included by the
installer builder.
- travis: build latest+nightly and deploy to bintray
- docs: link to the latest installer+info
- travis: disable s3 release, only build on cron
- bintray: use date as verion number
back-to