Skip to content

Commit a74f27b

Browse files
committed
Add to pip
1 parent 97395bb commit a74f27b

File tree

6 files changed

+33
-16
lines changed

6 files changed

+33
-16
lines changed

.gitignore

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -89,3 +89,4 @@ ENV/
8989

9090
# Rope project settings
9191
.ropeproject
92+
/.idea/

README.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
Beets plugin that fetches oldest recording or release date for each track. This is especially useful when tracks are from best-of compilations, remasters, or re-releases. Originally based on `beets-recordingdate` by tweitzel, but almost entirely rewritten to actually work with MusicBrainz's incomplete information. The only thing left intact is the `recording_` MP3 tags, for compatibility with `beets-recordingdate`.
33

44
# Installation
5-
Clone the repo and run `python setup.py install`, then add `oldestdate` to the list of active plugins in beets and configure as necessary. The plugin is intended to be used in singleton mode. Undefined behaviour may occur otherwise.
5+
Simply run `pip install beets-oldestdate` then add `oldestdate` to the list of active plugins in beets and configure as necessary. The plugin is intended to be used in singleton mode. Undefined behaviour may occur otherwise.
66

77
# Configuration
88

@@ -34,8 +34,6 @@ Clone the repo and run `python setup.py install`, then add `oldestdate` to the l
3434
filter_recordings: yes
3535
approach: 'releases'
3636

37-
38-
3937
## How it works
4038
The plugin will take the recording that was chosen and get its `work_id`. From this, it gets all recordings associated with said work. If using the `recordings` approach, it will look through these recordings' dates and find the oldest. If using the `releases` approach, it will instead go through the dates for all releases for all recordings and find the oldest (*much* more accurate). The difference between these two approaches is that with `recordings` it only takes one API call to get the necessary data, while with `releases` it takes *n* calls, where *n* is the number of recordings. This takes significantly longer due to MusicBrainz's default ratelimit of 1 API call per second. Due to this, the option `filter_recordings` exists to cut down on the amount of calls needed.
4139

beetsplug/__init__.py

Lines changed: 0 additions & 3 deletions
This file was deleted.

pyproject.toml

Lines changed: 31 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,31 @@
1+
[build-system]
2+
requires = ["hatchling"]
3+
build-backend = "hatchling.build"
4+
5+
[project]
6+
name = "beets-oldestdate"
7+
version = "1.1.3"
8+
authors = [
9+
{ name="kernitus" },
10+
]
11+
description = "Beets plugin that finds oldest possible track recording or release date"
12+
readme = "README.md"
13+
requires-python = ">=3.7"
14+
classifiers = [
15+
"Programming Language :: Python :: 3",
16+
"License :: OSI Approved :: MIT License",
17+
"Operating System :: OS Independent",
18+
]
19+
dependencies = [
20+
"mediafile~=0.9",
21+
"musicbrainzngs~=0.7",
22+
"python-dateutil~=2.8",
23+
"beets~=1.6",
24+
]
25+
26+
[project.entry-points.beetsplug]
27+
beets-oldestdate = "beets.oldestdate"
28+
29+
[project.urls]
30+
"Homepage" = "https://github.com/kernitus/beets-oldestdate"
31+
"Bug Tracker" = "https://github.com/kernitus/beets-oldestdate/issues"

requirements.txt

Lines changed: 0 additions & 4 deletions
This file was deleted.

setup.py

Lines changed: 0 additions & 6 deletions
This file was deleted.

0 commit comments

Comments
 (0)