instaloader/.travis.yml

language: python
python:
 - "3.5"
 - "3.5-dev"
 - "3.6"
 - "3.6-dev"
 - "3.7-dev"
 - "nightly"
install:
 - pip install pylint requests
script:
 - python3 -m pylint -r n -d bad-whitespace,missing-docstring,too-many-arguments,locally-disabled,line-too-long,too-many-public-methods,too-many-lines,too-many-instance-attributes instaloader
attempt to setup travis-ci to invoke pylint 2016-06-26 09:55:23 +02:00			`language: python`
			`python:`
			`- "3.5"`
Invoke pylint with all Python versions >= 3.3 We used to say in the project description text that we need Python>=3.2, but I just noted that we use print() flush parameter, which was introduced with python 3.3. Pylint would have warned that our code would fail with Python 3.2. 2016-06-26 10:33:17 +02:00			`- "3.5-dev"`
Fix very minor packaging issues - State in README.rst and setup.py metainfo that we require Python>=3.5 - Let Travis-CI test against newer versions of Python - Let instaloader --help show where to report issues 2017-02-13 09:57:03 +01:00			`- "3.6"`
Adjust travis yml 2016-12-22 13:24:50 +01:00			`- "3.6-dev"`
Fix very minor packaging issues - State in README.rst and setup.py metainfo that we require Python>=3.5 - Let Travis-CI test against newer versions of Python - Let instaloader --help show where to report issues 2017-02-13 09:57:03 +01:00			`- "3.7-dev"`
Invoke pylint with all Python versions >= 3.3 We used to say in the project description text that we need Python>=3.2, but I just noted that we use print() flush parameter, which was introduced with python 3.3. Pylint would have warned that our code would fail with Python 3.2. 2016-06-26 10:33:17 +02:00			`- "nightly"`
attempt to setup travis-ci to invoke pylint 2016-06-26 09:55:23 +02:00			`install:`
forgot about requests dependency -.- 2016-06-26 10:10:44 +02:00			`- pip install pylint requests`
attempt to setup travis-ci to invoke pylint 2016-06-26 09:55:23 +02:00			`script:`
Options --dirname-pattern and --filename-pattern Instaloader downloads all posts in <DIRNAME>/<FILENAME>+(suffix and extension) which are now generated by the templates given with --dirname-pattern and --filename-pattern. These templates may contain specifiers such as '{target}', '{profile}', '{date}' and '{shortcode}'. Default for --dirname-pattern is '{target}', default for --filename-pattern is '{date:%Y-%m-%d_%H-%M-%S}' The former options --no-profile-subdir and --hashtag-username were removed, because their behavior can now be achieved like this: --no-profile-subdir and --hashtag-username: --dirname-pattern='.' --filename-pattern='{profile}__{date:%Y-%m-%d_%H-%M-%S}' --no-profile-subdir, but not --hashtag-username: --dirname-pattern='.' --filename-pattern='{target}__{date:%Y-%m-%d_%H-%M-%S}' --hashtag-username but not --no-profile-subdir: --dirname-pattern='{profile}' This adds the option proposed in #23, to encode both the hashtag and the profile name in the file's path when downloading by hashtag, e.g.: --dirname-pattern='{target}' --filename-pattern='{profile}_{date:%Y-%m-%d_%H-%M-%S}' (Closes #23) 2017-07-25 18:31:08 +02:00			`- python3 -m pylint -r n -d bad-whitespace,missing-docstring,too-many-arguments,locally-disabled,line-too-long,too-many-public-methods,too-many-lines,too-many-instance-attributes instaloader`