What is version/release 0.33.3

[SebastianSchildt]

Here I see release 0.33.3: https://pypi.org/project/gps3/0.33.3/

But in this repo I do not find any such tag. What is the difference? Is Is the tag just missing, and can be added, otherwise it is a little bit unclear, how what you download from pypi s related to the source here

[wadda]

It's out of sync, I don't know if this if a typo, or an oversight, ...omission, or commission. I'll run a diff and straighten it out.

Thanks.

[SebastianSchildt]

Hi, sorry to nag, but any news? Technically this is no problem, but so far I cannot use the lib within an Eclipse Foundation project as external dependency. Their IP team denies it because for them it is unclear whether pypi 0.33.3 is also covered by the MIT license in this repo. A 0.33.3 tag would help....

[wadda]

It seems you have other problems other than two different repositories not being in sync.

It's my understanding if the github repository were non-existent the pypi files would still be covered under the MIT license.

The existence of this github repository does not change that license, if it matched the pypi repo, or if it didn't match, regardless of the content, or author.

Conversely, the existence of the pypi repository does not change this repository, or its legal status.

Your IT pals have taken umbrage, for something I have little interest in ferreting out, what particular is sticking in their craw?...which repository, files, or text should be deleted or changed to appease these folks, as, if you look closely, there are different versions numbers on different files throughout.

[rohoet]

If pypi provided the source files with a 0.33.3 tag, there would be no issue here. But as far as I can tell, sources are only available here.
There is only the need of mapping the pypi gps3-0.33.3-py2.py3-none-any.whl to source code - it could be a specific commit - a tag would be even better. This mapping is currently not clear to me.

If the official source code repository is hosted elsewhere, what is its location?

[wadda]

That's just it. pypi is providing exactly that. The title follows format, telling you what you need to know. The individual files within the archive are incremented on as needed, and not necessarily individually in lock step with the incremented package.

The .whl is an archive package of files...plus additional information files about the files, requisite locations/associations in the file structure yaddah yaddah....

The 'source code' code is/are the files themselves, except of the shebang-less. It's Python, These files don't, ...source code doesn't, get more fingertip to keyboard than that. So, I'm confused.

Grab a handy dandy archiver and take a look. (3 directories - 1 source files, 1 example files, 1 meta data and descriptor files)

As I recall, the scripts to create the .whl are included in the archive when the named version is packaged and posted to the repository, which for me was 'official'.

This github account, while trying to be the 'homepage' of the gps3 project's official repository, in spite of my best efforts is my public display of my hopes and box of broken dreams. The real embarrassments don't make it this far.

Any beginning to near end compendium to trace the provenance of the gps3 project is permanently stored on a bricked hard drive, and a backup with an irretrievable pass phrase. Clearly redundancy is for those who can't handle failure.

...so I'm really at a loss

[onkelbeh]

if somebody still searches this,
just hacked a replacement: https://github.com/onkelbeh/gps3/tree/0.33.3
I am using it for my Gentoo Home Assistant Overlay.
Compiles without problems on Python 3.7 and survived a short test.
I am not actively using it, just wanted it for the completeness of my Overlay.

[onkelbeh]

I don't understand what's so difficult on adding an additional tag (just want to get rid of the fork).
On Pypi, still there's only the WHL, please add an SDIST, or at least a appropriate tag here.
Or get it bumped in Home Assitant.