pyupcheck 0.3.2__tar.gz → 0.3.4__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- {pyupcheck-0.3.2 → pyupcheck-0.3.4}/PKG-INFO +16 -8
- {pyupcheck-0.3.2 → pyupcheck-0.3.4}/README.md +15 -7
- {pyupcheck-0.3.2 → pyupcheck-0.3.4}/depshift/__init__.py +1 -1
- {pyupcheck-0.3.2 → pyupcheck-0.3.4}/depshift/cli.py +7 -0
- {pyupcheck-0.3.2 → pyupcheck-0.3.4}/depshift/welcome.py +3 -3
- {pyupcheck-0.3.2 → pyupcheck-0.3.4}/pyproject.toml +1 -1
- {pyupcheck-0.3.2 → pyupcheck-0.3.4}/pyupcheck.egg-info/PKG-INFO +16 -8
- {pyupcheck-0.3.2 → pyupcheck-0.3.4}/LICENSE +0 -0
- {pyupcheck-0.3.2 → pyupcheck-0.3.4}/depshift/analyzer.py +0 -0
- {pyupcheck-0.3.2 → pyupcheck-0.3.4}/depshift/cache.py +0 -0
- {pyupcheck-0.3.2 → pyupcheck-0.3.4}/depshift/changelog.py +0 -0
- {pyupcheck-0.3.2 → pyupcheck-0.3.4}/depshift/config.py +0 -0
- {pyupcheck-0.3.2 → pyupcheck-0.3.4}/depshift/deps.py +0 -0
- {pyupcheck-0.3.2 → pyupcheck-0.3.4}/depshift/report.py +0 -0
- {pyupcheck-0.3.2 → pyupcheck-0.3.4}/depshift/scanner.py +0 -0
- {pyupcheck-0.3.2 → pyupcheck-0.3.4}/pyupcheck.egg-info/SOURCES.txt +0 -0
- {pyupcheck-0.3.2 → pyupcheck-0.3.4}/pyupcheck.egg-info/dependency_links.txt +0 -0
- {pyupcheck-0.3.2 → pyupcheck-0.3.4}/pyupcheck.egg-info/entry_points.txt +0 -0
- {pyupcheck-0.3.2 → pyupcheck-0.3.4}/pyupcheck.egg-info/requires.txt +0 -0
- {pyupcheck-0.3.2 → pyupcheck-0.3.4}/pyupcheck.egg-info/top_level.txt +0 -0
- {pyupcheck-0.3.2 → pyupcheck-0.3.4}/setup.cfg +0 -0
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
Metadata-Version: 2.4
|
|
2
2
|
Name: pyupcheck
|
|
3
|
-
Version: 0.3.
|
|
3
|
+
Version: 0.3.4
|
|
4
4
|
Summary: Check if upgrading a Python dependency will break your code
|
|
5
5
|
Author: AgbaDev
|
|
6
6
|
License-Expression: MIT
|
|
@@ -174,21 +174,29 @@ internal-package # no slash = package to skip
|
|
|
174
174
|
Contributions are welcome. Here is how to get started:
|
|
175
175
|
|
|
176
176
|
```bash
|
|
177
|
-
git clone https://github.com/
|
|
177
|
+
git clone https://github.com/Astronomox/pyupcheck-Astronomox.git
|
|
178
178
|
cd pyupcheck
|
|
179
|
-
pip install -e ".
|
|
179
|
+
pip install -e "."
|
|
180
180
|
```
|
|
181
181
|
|
|
182
|
-
|
|
182
|
+
**Releasing (for maintainers and forks)**
|
|
183
183
|
|
|
184
|
-
|
|
185
|
-
|
|
186
|
-
|
|
184
|
+
An `upload.bat` script is included to build and publish in one step. Get a PyPI API token from https://pypi.org/manage/account/token/ and run:
|
|
185
|
+
|
|
186
|
+
```
|
|
187
|
+
upload.bat YOUR_PYPI_TOKEN
|
|
188
|
+
```
|
|
189
|
+
|
|
190
|
+
It cleans old builds, builds the package, uploads to PyPI, installs the new version locally, and shows the banner to confirm. Never commit your token.
|
|
191
|
+
|
|
192
|
+
**Things that would genuinely improve the tool:**
|
|
193
|
+
|
|
194
|
+
- Better changelog parsing for packages that use unconventional formats (Sphinx-based changelogs, HISTORY files)
|
|
187
195
|
- `pip-tools` and `conda` lockfile support
|
|
188
196
|
- A `--watch` mode that monitors your lockfile for changes and alerts on risky upgrades
|
|
189
197
|
- Test coverage
|
|
190
198
|
|
|
191
|
-
To contribute, open an issue describing what you want to work on, then submit a pull request.
|
|
199
|
+
To contribute, open an issue describing what you want to work on, then submit a pull request. Include a short test or example showing the bug or feature.
|
|
192
200
|
|
|
193
201
|
If you find a package whose changelog pyupcheck fails to parse correctly, open an issue with the package name and version range. That is the most common and most impactful thing to fix.
|
|
194
202
|
|
|
@@ -152,21 +152,29 @@ internal-package # no slash = package to skip
|
|
|
152
152
|
Contributions are welcome. Here is how to get started:
|
|
153
153
|
|
|
154
154
|
```bash
|
|
155
|
-
git clone https://github.com/
|
|
155
|
+
git clone https://github.com/Astronomox/pyupcheck-Astronomox.git
|
|
156
156
|
cd pyupcheck
|
|
157
|
-
pip install -e ".
|
|
157
|
+
pip install -e "."
|
|
158
158
|
```
|
|
159
159
|
|
|
160
|
-
|
|
160
|
+
**Releasing (for maintainers and forks)**
|
|
161
161
|
|
|
162
|
-
|
|
163
|
-
|
|
164
|
-
|
|
162
|
+
An `upload.bat` script is included to build and publish in one step. Get a PyPI API token from https://pypi.org/manage/account/token/ and run:
|
|
163
|
+
|
|
164
|
+
```
|
|
165
|
+
upload.bat YOUR_PYPI_TOKEN
|
|
166
|
+
```
|
|
167
|
+
|
|
168
|
+
It cleans old builds, builds the package, uploads to PyPI, installs the new version locally, and shows the banner to confirm. Never commit your token.
|
|
169
|
+
|
|
170
|
+
**Things that would genuinely improve the tool:**
|
|
171
|
+
|
|
172
|
+
- Better changelog parsing for packages that use unconventional formats (Sphinx-based changelogs, HISTORY files)
|
|
165
173
|
- `pip-tools` and `conda` lockfile support
|
|
166
174
|
- A `--watch` mode that monitors your lockfile for changes and alerts on risky upgrades
|
|
167
175
|
- Test coverage
|
|
168
176
|
|
|
169
|
-
To contribute, open an issue describing what you want to work on, then submit a pull request.
|
|
177
|
+
To contribute, open an issue describing what you want to work on, then submit a pull request. Include a short test or example showing the bug or feature.
|
|
170
178
|
|
|
171
179
|
If you find a package whose changelog pyupcheck fails to parse correctly, open an issue with the package name and version range. That is the most common and most impactful thing to fix.
|
|
172
180
|
|
|
@@ -218,6 +218,13 @@ def main(ctx):
|
|
|
218
218
|
show_if_first_run(console)
|
|
219
219
|
|
|
220
220
|
|
|
221
|
+
@main.command("banner")
|
|
222
|
+
def show_banner():
|
|
223
|
+
"""Show the pyupcheck banner."""
|
|
224
|
+
from depshift.welcome import BANNER
|
|
225
|
+
console.print(BANNER)
|
|
226
|
+
|
|
227
|
+
|
|
221
228
|
# ── check ─────────────────────────────────────────────────────────────────────
|
|
222
229
|
|
|
223
230
|
@main.command()
|
|
@@ -1,11 +1,11 @@
|
|
|
1
1
|
"""Show a welcome banner on first run."""
|
|
2
2
|
|
|
3
|
-
import os
|
|
4
3
|
from pathlib import Path
|
|
4
|
+
from depshift import __version__
|
|
5
5
|
|
|
6
6
|
MARKER = Path.home() / ".cache" / "pyupcheck" / ".welcomed"
|
|
7
7
|
|
|
8
|
-
BANNER = """
|
|
8
|
+
BANNER = f"""
|
|
9
9
|
[bold cyan] ██████╗ ██╗ ██╗██╗ ██╗██████╗ ██████╗██╗ ██╗███████╗ ██████╗██╗ ██╗[/]
|
|
10
10
|
[bold cyan]██╔══██╗╚██╗ ██╔╝██║ ██║██╔══██╗██╔════╝██║ ██║██╔════╝██╔════╝██║ ██╔╝[/]
|
|
11
11
|
[bold cyan]██████╔╝ ╚████╔╝ ██║ ██║██████╔╝██║ ███████║█████╗ ██║ █████╔╝ [/]
|
|
@@ -15,7 +15,7 @@ BANNER = """
|
|
|
15
15
|
|
|
16
16
|
[bold white] Know if a dependency upgrade will break your code before you run it.[/]
|
|
17
17
|
|
|
18
|
-
[dim]Version[/] [green]
|
|
18
|
+
[dim]Version[/] [green]{__version__}[/]
|
|
19
19
|
[dim]PyPI[/] [blue]https://pypi.org/project/pyupcheck[/]
|
|
20
20
|
[dim]GitHub[/] [blue]https://github.com/Astronomox/pyupcheck-Astronomox[/]
|
|
21
21
|
[dim]Author[/] [cyan]AgbaDev (Astronomox)[/]
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
Metadata-Version: 2.4
|
|
2
2
|
Name: pyupcheck
|
|
3
|
-
Version: 0.3.
|
|
3
|
+
Version: 0.3.4
|
|
4
4
|
Summary: Check if upgrading a Python dependency will break your code
|
|
5
5
|
Author: AgbaDev
|
|
6
6
|
License-Expression: MIT
|
|
@@ -174,21 +174,29 @@ internal-package # no slash = package to skip
|
|
|
174
174
|
Contributions are welcome. Here is how to get started:
|
|
175
175
|
|
|
176
176
|
```bash
|
|
177
|
-
git clone https://github.com/
|
|
177
|
+
git clone https://github.com/Astronomox/pyupcheck-Astronomox.git
|
|
178
178
|
cd pyupcheck
|
|
179
|
-
pip install -e ".
|
|
179
|
+
pip install -e "."
|
|
180
180
|
```
|
|
181
181
|
|
|
182
|
-
|
|
182
|
+
**Releasing (for maintainers and forks)**
|
|
183
183
|
|
|
184
|
-
|
|
185
|
-
|
|
186
|
-
|
|
184
|
+
An `upload.bat` script is included to build and publish in one step. Get a PyPI API token from https://pypi.org/manage/account/token/ and run:
|
|
185
|
+
|
|
186
|
+
```
|
|
187
|
+
upload.bat YOUR_PYPI_TOKEN
|
|
188
|
+
```
|
|
189
|
+
|
|
190
|
+
It cleans old builds, builds the package, uploads to PyPI, installs the new version locally, and shows the banner to confirm. Never commit your token.
|
|
191
|
+
|
|
192
|
+
**Things that would genuinely improve the tool:**
|
|
193
|
+
|
|
194
|
+
- Better changelog parsing for packages that use unconventional formats (Sphinx-based changelogs, HISTORY files)
|
|
187
195
|
- `pip-tools` and `conda` lockfile support
|
|
188
196
|
- A `--watch` mode that monitors your lockfile for changes and alerts on risky upgrades
|
|
189
197
|
- Test coverage
|
|
190
198
|
|
|
191
|
-
To contribute, open an issue describing what you want to work on, then submit a pull request.
|
|
199
|
+
To contribute, open an issue describing what you want to work on, then submit a pull request. Include a short test or example showing the bug or feature.
|
|
192
200
|
|
|
193
201
|
If you find a package whose changelog pyupcheck fails to parse correctly, open an issue with the package name and version range. That is the most common and most impactful thing to fix.
|
|
194
202
|
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|