pyupcheck 0.3.3__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.
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.4
2
2
  Name: pyupcheck
3
- Version: 0.3.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/AgbaDev/pyupcheck.git
177
+ git clone https://github.com/Astronomox/pyupcheck-Astronomox.git
178
178
  cd pyupcheck
179
- pip install -e ".[dev]"
179
+ pip install -e "."
180
180
  ```
181
181
 
182
- Things that would genuinely improve the tool:
182
+ **Releasing (for maintainers and forks)**
183
183
 
184
- - Better changelog parsing for packages that use unconventional formats (e.g. Sphinx-based changelogs, HISTORY files)
185
- - Support for `setup.cfg` and `setup.py` dependency parsing
186
- - Detection of dynamic attribute access patterns (`getattr`, `__import__`)
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. Please include a short test or example showing the bug or feature.
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/AgbaDev/pyupcheck.git
155
+ git clone https://github.com/Astronomox/pyupcheck-Astronomox.git
156
156
  cd pyupcheck
157
- pip install -e ".[dev]"
157
+ pip install -e "."
158
158
  ```
159
159
 
160
- Things that would genuinely improve the tool:
160
+ **Releasing (for maintainers and forks)**
161
161
 
162
- - Better changelog parsing for packages that use unconventional formats (e.g. Sphinx-based changelogs, HISTORY files)
163
- - Support for `setup.cfg` and `setup.py` dependency parsing
164
- - Detection of dynamic attribute access patterns (`getattr`, `__import__`)
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. Please include a short test or example showing the bug or feature.
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
 
@@ -1,3 +1,3 @@
1
1
  """depshift - Check if upgrading a Python dependency will break your code."""
2
2
 
3
- __version__ = "0.3.3"
3
+ __version__ = "0.3.4"
@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
4
4
 
5
5
  [project]
6
6
  name = "pyupcheck"
7
- version = "0.3.3"
7
+ version = "0.3.4"
8
8
  description = "Check if upgrading a Python dependency will break your code"
9
9
  readme = "README.md"
10
10
  license = "MIT"
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.4
2
2
  Name: pyupcheck
3
- Version: 0.3.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/AgbaDev/pyupcheck.git
177
+ git clone https://github.com/Astronomox/pyupcheck-Astronomox.git
178
178
  cd pyupcheck
179
- pip install -e ".[dev]"
179
+ pip install -e "."
180
180
  ```
181
181
 
182
- Things that would genuinely improve the tool:
182
+ **Releasing (for maintainers and forks)**
183
183
 
184
- - Better changelog parsing for packages that use unconventional formats (e.g. Sphinx-based changelogs, HISTORY files)
185
- - Support for `setup.cfg` and `setup.py` dependency parsing
186
- - Detection of dynamic attribute access patterns (`getattr`, `__import__`)
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. Please include a short test or example showing the bug or feature.
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