aboutsummaryrefslogtreecommitdiffstats
path: root/setup.py
Commit message (Collapse)AuthorAgeFilesLines
* Add pyproject.toml and switch to setup.cfg with only a skeleton setup.py.Ben Sturmfels2021-04-081-147/+3
|
* Simplify packaging of static assets.Ben Sturmfels2021-04-071-9/+1
|
* Include static assets in setuptools package.Ben Sturmfels2021-04-071-3/+8
|
* Document setup.py data_files.Ben Sturmfels2021-04-061-0/+2
|
* Include env.py in Python package.Ben Sturmfels2021-04-061-0/+1
|
* Now in the 0.12.0 development cycle.Ben Sturmfels2021-04-051-2/+2
|
* fixup! Pin werkzeug to fix breaking tests.Ben Sturmfels2021-04-041-1/+1
|
* Pin werkzeug to fix breaking tests.Ben Sturmfels2021-04-041-1/+1
|
* Fix extras_require.Ben Sturmfels2021-04-041-1/+4
|
* Move WebTest requirement to "extras_require".Ben Sturmfels2021-04-021-2/+2
|
* Remove implicit dependency on PasteDeploy.Ben Sturmfels2021-04-021-1/+0
| | | | This is installed by PasteScript.
* Sort the dependencies in setup.py for easy comparison with guix-env.scm.Ben Sturmfels2021-04-011-24/+20
|
* Fix pytest issues in Guix.Ben Sturmfels2021-03-301-2/+5
| | | | | | | Key here was removing pytest-xdist from setup.py's "install_requires" list. Otherwise running the test suite under Guix would fail with something like: pkg_resources.ContextualVersionConflict: (pytest 5.3.5 (/gnu/store/9clwgf5svincpw3fbjcijdlw9mylyzn3-profile/lib/python3.8/site-packages), Requirement.parse('pytest>=6.0.0'), {'pytest-xdist'})
* Fix audio and submission tests under Guix.Ben Sturmfels2021-03-301-1/+1
| | | | | | | | Have temporarily included libsndfile and python-soundfile until these changes get merged into Guix upstream. Identified that Guix's older python-wtforms 2.1 is not compatible with the test suite.
* Add "feedgenerator" requirement to setup.py.Ben Sturmfels2021-03-291-0/+1
|
* Convert atom feeds to use feedgenerator library.Ben Sturmfels2021-03-161-1/+1
| | | | | | | | | | | | | | | Issue is that Werkzeug > 1.0.0 has removed werkzeug.contrib.atom.AtomFeed, making it difficult to use a distribution-packaged version of werkzeug. To solve this, I've replaced use of werkzeug.contrib.atom.AtomFeed with feedgenerator.Atom1Feed. After the change, the only major difference between the feeds before and after is that they use <summary> instead of <content>. Minor differences include no longer adding 'type="text/html"' on some <link> elements and no "xml:base" attribute on <entry> elements. I don't think these differences will have any noticable effect. Tested on Liferea feed reader.
* Pin sqlalchemy to a known good version.Charlotte Koch2021-03-061-1/+1
| | | | | | | | The latest version is 1.4.0b1 which changes some internals a bit... internals which unforuntately mediagoblin's DatabaseManager screw around with (namely, _decl_class_registry) Signed-off-by: Ben Sturmfels <ben@sturm.com.au>
* Apply `pyupgrade --py3-plus` to remove Python 2 compatibility code.Ben Sturmfels2021-03-051-3/+1
|
* Remove six library.Ben Sturmfels2021-03-051-1/+0
|
* Reinstate audio spectrograms on Python 3 [#5610].Fernando Gutierrez2021-03-031-0/+2
| | | | | | | | The `audiotospectrogram` module is a complete rewrite of the existing spectrogram code with support for Python 3. This allows us to drop the bundled `freesound` library and Python 2-only `audioprocessing` and `spectrogram` modules. Signed-off-by: Ben Sturmfels <ben@sturm.com.au>
* Drop Python 2 installation support.Ben Sturmfels2021-03-031-88/+2
|
* Pin wtforms due to removal of ext module.Ben Sturmfels2021-03-031-1/+2
|
* docs: Tweak the release notes and deployment docs following testing.Ben Sturmfels2020-05-041-0/+1
|
* Allow Python 2 minor version upgrades [#5595].Ben Sturmfels2020-04-301-77/+77
|
* Forcibly pin all Python 2 dependencies [#5595].Ben Sturmfels2020-04-301-11/+77
| | | | | This is really horrible, but seems like the only way to stop Python 2 installs breaking randomly in the future.
* Fix Python 2 package dependencies and sub-dependencies [#5595].Ben Sturmfels2020-04-301-2/+7
| | | | | | | | | | | This fixes the installation process *right now* on Python 2. The problem is that packages are dropping Python 2 support all over the place and due to our (deliberate) loose dependency version specifications and the loose sub-dependency version specifications, it's one horrible mess. But it works right now. Next up I'll be pinning all the currently installed Python 2 packages and all dependencies.
* Fix dependencies and tests for clean Python 2 & 3 test runs under Docker.Ben Sturmfels2020-04-281-2/+5
| | | | | This change gives a clean test run in the Debian-based Python 2 and Python 3 docker images.
* Fix "KeyError: 'No such transport: sqlite. Did you mean sqla?'" in tests.Ben Sturmfels2020-04-141-1/+2
| | | | | This is caused by Celery dropping the "sqlite" transport alias from version 4.3.0, so I've pinned an upper limit.
* Require jinja2<3.0.0 due to use of f-strings.Ben Sturmfels2020-04-101-1/+3
|
* Pin werkzeug < 1.0.0.Ben Sturmfels2020-04-011-1/+1
| | | | In 1.0.0, the werkzeug.contrib module was removed which was required for `werkzeug.contrib.atom.AtomFeed`.
* require higher version of six due to installation problemsBoris Bobrov2018-08-131-1/+1
|
* Revert "cap sqlalchemy"Boris Bobrov2018-06-081-1/+1
| | | | | | This reverts commit d803f14361ec02878afe4f6b196ce917010a1e2f. WTForms 2.2 was releases, see https://issues.mediagoblin.org/ticket/5570#comment:6
* cap sqlalchemyBoris Bobrov2018-04-301-1/+1
| | | | Closes #5557 and fixes some complaints in irc
* move exifread to other dependenciesBoris Bobrov2017-06-101-3/+1
|
* Remove upper cap on celery kombuBoris Bobrov2017-06-101-2/+1
| | | | Also remove kombu from requirements, because celery fetches it anyway
* Modify setup.py version syntax to address #5464Andrew Browning2016-08-261-2/+2
| | | | | | | | | Some users report that even with version <4.0 specified in setup.py, the 4.0-rc builds of kombu and celery were still being downloaded. This patch uses a different version syntax as suggested in a Stack Overflow thread. https://stackoverflow.com/a/14405269
* Cap kombu and celeryBoris Bobrov2016-07-251-2/+2
| | | | See issue 5464 for details
* Remove old hack to support pre-0.7.5 Alembic versionsChristopher Allan Webber2016-03-021-1/+1
| | | | | Thanks to Jessica Tallon for pointing out this TODO and its associated hack could be removed.
* Remove version caps on sqlalchemy and alembic.Christopher Allan Webber2016-03-021-2/+2
| | | | | Code seems to pass fine after the cap is removed. Whatever dependency issues we were running into before don't seem to be an issue now.
* Oh, we don't need Paste, but we do need PasteScript!Christopher Allan Webber2016-02-201-0/+1
|
* Removing python 2.6 junk: argparse and a 2.6 classifierChristopher Allan Webber2016-02-191-2/+0
|
* Switch from Paste for serving to WaitressChristopher Allan Webber2016-02-191-4/+1
| | | | | Incredibly, it looks like none of our documentation has to change taking this route...!
* Cleanup setup.pyBoris Bobrov2016-02-181-8/+0
| | | | Remove old comments and duplicate requirements from setup.py
* Removed deprecated comment about wsgi environ being borkedChristopher Allan Webber2016-02-171-2/+0
|
* Upgrade sqlalchemy and sa-migrateBoris Bobrov2016-02-111-2/+2
| | | | Our versions were too old. And not compatible with python3.
* Uncap PasteBoris Bobrov2016-01-071-1/+1
| | | | | Paste was capped to 1.9.9 because 2.0 broke us. Now Paste 2.0.x was released and it doesn't break us any more. Closes bug 5317.
* Switch to webtest >= 2.0.18Christopher Allan Webber2015-11-051-1/+1
|
* trac#665: Upgrade to WebTest 2.0.18 and fix broken test `test_csrf_cookie_set`.Ben Sturmfels2015-11-051-1/+1
| | | | | | | | Test was failing due to API change in WebTest around accessing cookies set in the test client. These are now in `test_app.cookies`. While there are currently 48 other tests failing, I've verified that before and after this change that the same number fail. I've also checked that no other tests use the old API for accessing test client cookies. I've pinned to version 2.0.18. My understanding is that it's generally a good idea to pin to a specific version where possible to avoid the "why has this suddenly broken" type bugs. This also seems appropriate since WebTest appears to be very stable.
* Pin mock 1.0.1 in Python 2 for now.Berker Peksag2015-07-221-1/+1
| | | | | | | | | mock recently dropped Python 2.6 support and then re-introduced it in its latest release (however, it's a bit unstable right now). I think at this point, we can be more cautious and just use mock==1.0.1.
* Paste 2.0 breaking wsgiChristopher Allan Webber2015-04-241-1/+3
|
generated by cgit v1.2.3 (git 2.25.1) at 2025-06-07 09:20:16 +0000