Skip to content

Release InstaPy on PyPi with versioning#3887

Merged
timgrossmann merged 65 commits intomasterfrom
dev
Feb 4, 2019
Merged

Release InstaPy on PyPi with versioning#3887
timgrossmann merged 65 commits intomasterfrom
dev

Conversation

@timgrossmann
Copy link
Copy Markdown
Collaborator

Version [0.1.1] - 2019-02-04

Added

  • Workspace folders; Now user's data files will be stored at the workspace folder.
  • InstaPy has been published to PyPI; Now, can install/manage it by pip as instapy package.
  • Github releases has been initiated; Will be released in-parallel with PyPI deployments.
  • Add Universal Testing Framework- tox with pytest & flake8.
  • Upgrade Travis CI usage (tox as build script).
  • Send messages to Discord #status channel about jobs' build states from Travis CI.
  • Add instapy-chromedriver package if no chromedriver is in path
  • Add argparse feature. Users are now able to provide credentials (and more) through CLI args

Note that the legacy branch will stay at the state of the old InstaPy structure.

uluQulu and others added 30 commits January 12, 2019 02:46
From now on, assets folder is gonna reside at user's workspace folder.
*chromedriver will be there too
It is best to have InstaPy extensions get through pip.
When instapy package is installed through pip then icons folder will reside inside the instapy folder.
Without this change, it would reside in a separate folder at the same level with instapy package which is not good.

With setuptools it is impossible to make it work otherwise (it was possible with old distutils).
… & make a sample test file

Although those old tests are deprecated and incompatible with today's code, they are very decent and written by a tester professional.
So that, it's best to fix the incompatibilities in them and serve them as strong tests to be run by pytest.
From now on, it will reside in the user's workspace folder and operate as before.

All of the files will be generated during runtime as requested.
Having version information stored here will help to get it as ```instapy.__version__```

Also, it will ease changing version number each time from here rather than from setup.py[setup()].
…le to be imported to other modules easily.

In future can write other custom-exceptions here in the same file.
… better handling and stability

It checks the current chromedriver locations if exists, if not makes sure assets folder exist and then asks user to put chromedriver executable to that folder.
…on or from pip's install location using pkg_resources module
…ew priority to highlight_print()

And relocate imports.
…ckage of plyer package for old pythons

 - Since new plyer is available (2 new versions released) the bug with python 2.7 has been resolved.
 Now it will work for 2.7.15 and in future if verified, can be enabled for olders, too.

 - Some other visual changes, pass a logfolder, etc.
It is highly flexible and acts as before.
Apparently, you can set custom locations like,
Settings.database_locations = "home\dbis\instapy.db"
any time.
File managemer module is wrriten to handle every worse scenario.
set_workspace() function here is part of user interface and get_workspace() can also be used like so.
Changes:
 - `python_requires` refined;
 - remove deprecated `classifiers`
 - add new packages to extra test requirements;
 - update keywords;
 - use package_data to bundle data files into distributions
 - get version info from __init__.py module
 - update summary;
 - load README.md and data from __init__.py using re and io modules;
 - add a few more project URLs and remove deprecated
Run multi-python tests with pytest and also static analysis tests with flake8.
…es. also auto-deploy to PyPI & Discord notifications
There was a missing , between the parameters
timgrossmann and others added 18 commits January 27, 2019 16:42
added instapy-chromedriver package if no chromedriver is in path
Remove
- `set_relationship_bounds()`
- `set_dont_like()`
- login credentials example
- headless mode example
Extras
- choose editable install (`-e` flag) for advanced installation
- some <br /> newlines for good structural look
- align the position of donation buttons for good looks
- add 3 horizontal space to Discord's button for good looks xD
- other neat visual changes
…lags conflicting with reserved args.

Supports Python >= 2.7

See https://docs.python.org/3/library/argparse.html#allow-abbrev to understand more of this behaviour.
@timgrossmann timgrossmann changed the title Release InstaPy on PI with versioning Release InstaPy on PyPi with versioning Feb 4, 2019
@tE3m
Copy link
Copy Markdown
Contributor

tE3m commented Feb 4, 2019

Great! So now that InstaPy is live on PyPi, should users move from the "old" GitHub version to the PyPi version? And if so, how do we transfer our database?

@timgrossmann
Copy link
Copy Markdown
Collaborator Author

@TarekJ03 Takes another half an hour 😉
Everything is described in the readme then.

Simply copy&paste the content of your logs folder to the logs folder that will be created with the first run of InstaPy installed with pip.

You can still use the InstaPy from GitHub, the master branch will hold the same state.
You can still do the installation by going into the cloned repo and doing pip install .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants