Closed zaneselvans closed 11 months ago
Hmmm... I'd wager this is not a croniter-feedstock problem, as this installs correctl. It's possible #53 would fix this. But the wheel metadata no longer reflects the LICENSE, which may confuse the conda list
mechanism.
│ --- croniter-1.4.1.dist-info/METADATA
├── +++ croniter-2.0.0.dist-info/METADATA
│┄ Files 2% similar despite different names
│ @@ -1,10 +1,10 @@
│ Metadata-Version: 2.1
│ Name: croniter
│ -Version: 1.4.1
│ +Version: 2.0.0
│ Summary: croniter provides iteration for datetime object with cron like format
│ Home-page: http://github.com/kiorky/croniter
│ Author: Matsumoto Taichi, kiorky
│ Author-email: taichino@gmail.com, kiorky@cryptelium.net
│ License: MIT License
│ Keywords: datetime,iterator,cron
│ Platform: UNKNOWN
│ @@ -21,18 +21,19 @@
│ Classifier: Programming Language :: Python :: 3.5
│ Classifier: Programming Language :: Python :: 3.6
│ Classifier: Programming Language :: Python :: 3.7
│ Classifier: Programming Language :: Python :: 3.8
│ Classifier: Programming Language :: Python :: 3.9
│ Classifier: Programming Language :: Python :: 3.10
│ Classifier: Programming Language :: Python :: 3.11
│ +Classifier: Programming Language :: Python :: 3.12
│ Classifier: Topic :: Software Development :: Libraries :: Python Modules
│ Requires-Python: >=2.6, !=3.0.*, !=3.1.*, !=3.2.*, !=3.3.*
│ -License-File: LICENSE
│ Requires-Dist: python-dateutil
│ +Requires-Dist: pytz (>2021.1)
May be related to this:
@bollwyvl the wheel (for 2.0.0
) installs correctly via pip
but conda list
still fails due to the bad metadata. Agreed this is not a feedstock problem.
I'll reopen conda/conda#10371 as a new issue and start working on a PR to fix the assertion. In practice, this wheel should be fixed as currently it breaks any conda environment that pulls it in. But technically https://peps.python.org/pep-0376/#record
doesn't make any assertions about it being uppercase vs. lowercase.
Currently this is breaking many of our docker images so hoping to see if we can work w/ @kiorky to push a fixed wheel.
For anyone else running into this, I've opened a PR in conda to address some related issues there. That'll take a while to be merged in though and this package as written is technically non-conformant.
Recommended workaround is to pin <2.0.0 if installing via pip or install directly via conda (not always possible if it's pulled in as a dependency).
Thanks so much for jumping on this @iamthebot! It's always nice when taking the time to report a bug results in a fix.
For the LICENSE inclusion, 2.0.1 is out.
Tested the failing scenario, i reproduce the error with 2.0.0, but not with 2.0.1, closing as fixed.
I'm not exactly sure where it is happening, but with the release of 2.0.0 I am getting an
AssertionError
after installingcroniter==2.0.0
inside a conda environment usingpip
, and it seems to be unhappy that the package hash starts withSHA256=
rather thansha256=
. Was there a change in thecroniter
packaging system between 1.4.1 and 2.0.0?Or maybe this makes more sense to one of the conda feedstock maintainers @mariusvniekerk @bollwyvl? Or maybe it's a problem with how
mamba
/conda
is parsing the package metadata? I'm unsure.To reproduce the error: