-
Notifications
You must be signed in to change notification settings - Fork 135
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
New release on pypi #368
Comments
Sorry to hear you had a bad experience. pip install https://github.com/turicas/rows/archive/develop.zip |
@turicas Great to hear that you're planning a new release in the short term. |
Any update about a new release on pypi ? |
So, what about the release on pypi ? |
Example of code that I have to write to block users using pypi for rows: |
I had to add weird patches to Debian vendoring some parts of old |
@turicas Do you still plan to make a release on pypi some day, or did you choose to continue without releasing on pypi ? |
As new year resolution for 2025, I propose "make a new release on pypi" :) |
I started using the "rows" lib today, and I've lost several hours of work because of a bug on empty cells in ods input. Here is my story.
I was learning/discovering the "rows" lib with an ODS file, and I fall across a strange behavior. Of course, I thought it was because I didn't use the lib properly : so I tried all possible options, searched on the Internet... etc. After several hours, I eventually tried the same code with an equivalent XLSX file and I found out that the behavior was different ! So I realized that I had found a bug on my first day of use of the rows lib !
I decided that I should report the bug. I took the time to write a script to illustrate my bug report. I was using rows 0.4.1 from pypi, but, before creating the bug report on github, I thought I should check if the bug is still present in the "develop" branch... and my script shows that the bug is fixed in the "develop" branch !
Release 0.4.1 is dated Feb 14, 2019... almost 4 years old ! There has been 210 commits since 0.4.1 ; among these 210 commits, I counted about 45 fixes. While counting the commit messages with a fix message, I found the commit that fixes my bug: issue #320 fixed on Match 27 2019 in this commit c569f94
So, in December 2022, some users are wasting hours because of a bug that was found and fixed 3,5 years ago :-( No comment !
So, please, push a new release on pypi !
The text was updated successfully, but these errors were encountered: