2013-02-18 23:23:44 +01:00
|
|
|
*.class
|
2011-07-29 01:11:56 +02:00
|
|
|
*.pyc
|
|
|
|
|
*.pyo
|
|
|
|
|
*.o
|
|
|
|
|
*.so
|
|
|
|
|
*.os
|
|
|
|
|
*.pyd
|
|
|
|
|
*.elc
|
|
|
|
|
*~
|
|
|
|
|
.*.swp
|
|
|
|
|
.*.swo
|
|
|
|
|
.*.swn
|
|
|
|
|
.~
|
2018-06-12 03:27:09 +02:00
|
|
|
.envrc
|
2011-07-29 01:11:56 +02:00
|
|
|
.DS_Store
|
|
|
|
|
.ropeproject
|
|
|
|
|
ID
|
|
|
|
|
__pycache__/
|
2020-11-15 22:57:53 +01:00
|
|
|
**/build/
|
|
|
|
|
**/dist/
|
2015-09-17 19:58:22 +02:00
|
|
|
/*.egg*
|
2011-07-29 02:02:28 +02:00
|
|
|
/MANIFEST
|
2011-07-29 03:14:09 +02:00
|
|
|
/README.html
|
2011-08-01 22:39:16 +02:00
|
|
|
/pypi-server-standalone.py
|
2014-11-14 01:11:34 +01:00
|
|
|
/.project
|
|
|
|
|
/.pydevproject
|
2018-06-12 03:27:09 +02:00
|
|
|
/.pytest_cache
|
2011-08-30 02:37:25 +02:00
|
|
|
/.tox/
|
2020-11-15 22:57:53 +01:00
|
|
|
**/*.egg-info/
|
2015-09-11 16:45:29 +02:00
|
|
|
/.standalone
|
2020-10-09 02:37:39 +02:00
|
|
|
/.coverage*
|
Refactor storage operations into separate Backend classes (#348)
Following the discussion in #253 and #325 I've created a first iteration on what a `Backend` interface could look like and how the current file storage operations may be refactored into this interface. It goes from the following principles
* `app.py` talks only to `core.py` with regards to package operations
* at configuration time, a `Backend` implementation is chosen and created for the lifetime of the configured app
* `core.py` proxies requests for packages to this `Backend()`
* The `Backend` interface/api is defined through three things
* methods that an implementation must implement
* methods that an implementation may override if it knows better than the defaults
* the `PkgFIle` class that is (should be) the main carrier of data
* where possible, implementation details must be hidden from concrete `Backend`s to promote extensibility
Other things I've done in this PR:
* I've tried to talk about packages and projects, rather than files and prefixes, since these are the domain terms PEP503 uses, and imho it's also more clear what it means
* Better testability of the `CacheManager` (no more race conditions when `watchdog` is installed during testing)
* Cleanup some more Python 2 code
* Started moving away from `os.path` and `py.path` in favour of `pathlib`
Furthermore I've created a `plugin.py` with a sample of how I think plugin system could look like. This sampIe assumes we use `argparse` and allows for the extension of cli arguments that a plugin may need. I think the actual implementation of such a plugin system is beyond the scope of this PR, but I've used it as a target for the Backend refactoring. If requested, I'll remove it from this PR.
The following things still need to be done / discussed. These can be part of this PR or moved into their own, separate PRs
- [ ] Simplify the `PgkFile` class. It currently consists of a number of attributes that don't necessarily belong with it, and not all attributes are aptly named (imho). I would like to minimalize the scope of `PkgFile` so that its only concern is being a data carrier between the app and the backends, and make its use more clear.
- [ ] Add a `PkgFile.metadata` that backend implementations may use to store custom data for packages. For example the current `PkgFile.root` attribute is an implementation detail of the filestorage backends, and other Backend implementations should not be bothered by it.
- [ ] Use `pathlib` wherever possible. This may also result in less attributes for `PkgFile`, since some things may be just contained in a single `Path` object, instead of multtiple strings.
- [ ] Improve testing of the `CacheManager`.
----
* move some functions around in preparation for backend module
* rename pkg_utils to pkg_helpers to prevent confusion with stdlib pkgutil
* further implement the current filestorage as simple file backend
* rename prefix to project, since that's more descriptive
* add digester func as attribute to pkgfile
* WIP caching backend
* WIP make cache better testable
* better testability of cache
* WIP file backends as plugin
* fix typos, run black
* Apply suggestions from code review
Co-authored-by: Matthew Planchard <mplanchard@users.noreply.github.com>
* add more type hints to pass mypy, fix tox.ini
* add package count method to backend
* add package count method to backend
* minor changes
* bugfix when checking invalid whl file
* check for existing package recursively, bugfix, some more pathlib
* fix unittest
* rm dead code
* exclude bottle.py from coverage
* fix merge mistakes
* fix tab indentation
* backend as a cli argument
* fix cli, add tests
* fix mypy
* fix more silly mistakes
* process feedback
* remove dead code
Co-authored-by: Matthew Planchard <mplanchard@users.noreply.github.com>
2021-02-02 18:44:29 +01:00
|
|
|
!/.coveragerc
|
2013-01-04 02:09:11 +01:00
|
|
|
/htmlcov/
|
|
|
|
|
/.installed.cfg
|
|
|
|
|
/develop-eggs/
|
|
|
|
|
/eggs/
|
|
|
|
|
/parts/
|
2015-09-19 02:36:43 +02:00
|
|
|
/.cache/
|
2014-11-14 12:07:11 +01:00
|
|
|
/.settings/
|
2017-10-31 15:32:12 +01:00
|
|
|
.mypy_cache/
|
Update Tests for New Twine
* Updated .travis.yml to fix PEP 440 warnings
* Fixed twine calls
We were getting test failures on multiple branches in
`test_server.py`. I first investigated a warning message
popping up in every test run:
```
PEP440Warning,
/home/travis/virtualenv/python3.5.2/lib/python3.5/site-packages/pkg_resources/__init__.py:2510: PEP440Warning: 'setuptools (git-0.4.0)' is being parsed as a legacy, non PEP 440, version. You may find odd behavior and sort order. In particular it will be sorted as less than 0.0. It is recommend to migrate to PEP 440 compatible versions.
```
Moving the installation of setuptools, pip, sphinx, and tox
into the `install` key for Travis resolved that issue, but
`test_server.py` tests were still failing. It turns out that
Twine 1.7.0 added support for SSL cert specification and,
in the process, changed the call signature for the `upload`
and `register` internal methods.
This PR fixes the calls so that they align with Twine's new
function signature. Note that tests now fail on Twine <1.7.0,
so I have also updated the dev requirements file.
2016-07-17 20:40:06 +02:00
|
|
|
|
|
|
|
|
# IDE stuff
|
|
|
|
|
.idea/
|
2018-06-12 03:27:09 +02:00
|
|
|
.vscode/
|
2017-10-31 15:32:12 +01:00
|
|
|
|
|
|
|
|
# Venvs
|
|
|
|
|
.venv/
|
|
|
|
|
venv/
|
|
|
|
|
|