[x3d-public] x3d.py package: Some feedback and suggestion for improvement; tuples and lists; updated x3d.py

[Hans Moritz Guenther]

On 3/5/22 9:08 PM, Brutzman, Donald (Don) (CIV) wrote:
>
> Thanks Moritz for looking at this.  However, we can’t really expect 
> any PyPi user who types “pip install x3d” to go through such a process.
>
A Pypi user does not have to go through that - unless their local 
installation is messed up in some way; I was just trying to debug. 
Plenty of Pypi packages work just like that.


However, right now the problem seems to be different:

Something changed in the Pypi setup for this package between 4.0.57 and 
4.0.58: From 4.0.58 on, "pip install" only downloads and installs the 
metadata of the package (license file etc.), but not the actual code. 
Note in the following output how an installation with 4.0.57 gives me 
two directories in my "site-packages" called "x3d" (with the code) and 
"x3d-4.0.57-py3-none-any.whl" (with the meta data of the package).

However, starting with 4.0.58, I ONLY get the metadata and not the 
actual code - and thus an "import x3d" must fail just because the code 
is not actually installed. It also no longer downloads the actual ~400 
kB wheel:


(kitchensink) MoritzAirRoseGold 
~/mambaforge/envs/kitchensink/lib/python3.10> pip install x3d==4.0.56
Collecting x3d==4.0.56
   Downloading x3d-4.0.56-py3-none-any.whl (418 kB)
      |████████████████████████████████| 418 kB 2.3 MB/s
Installing collected packages: x3d
   Attempting uninstall: x3d
     Found existing installation: x3d 4.0.52
     Uninstalling x3d-4.0.52:
       Successfully uninstalled x3d-4.0.52
Successfully installed x3d-4.0.56
(kitchensink) MoritzAirRoseGold 
~/mambaforge/envs/kitchensink/lib/python3.10> ls site-packages/x3*
site-packages/x3d:
__init__.py __pycache__ x3d.py

site-packages/x3d-4.0.56.dist-info:
INSTALLER     LICENSE       METADATA      RECORD REQUESTED     
WHEEL         license.html  license.txt top_level.txt
(kitchensink) MoritzAirRoseGold 
~/mambaforge/envs/kitchensink/lib/python3.10> pip install x3d==4.0.57
Collecting x3d==4.0.57
   Downloading x3d-4.0.57-py3-none-any.whl (16 kB)
Installing collected packages: x3d
   Attempting uninstall: x3d
     Found existing installation: x3d 4.0.56
     Uninstalling x3d-4.0.56:
       Successfully uninstalled x3d-4.0.56
Successfully installed x3d-4.0.57
(kitchensink) MoritzAirRoseGold 
~/mambaforge/envs/kitchensink/lib/python3.10> ls site-packages/x3*
INSTALLER     LICENSE       METADATA      RECORD REQUESTED     
WHEEL         license.html  license.txt top_level.txt



How do you upload the package to Pypi? By hand? Do you use some uploader 
script or do it by hand?

If you follow for example 
https://packaging.python.org/en/latest/tutorials/packaging-projects/ :

- When you do "python -m build" in your local directory, do you see the 
actual code file (the .tar.gz file) or only the wheel metadata (the whl 
file)?

- When you upload (python3 -m twine upload ....) do you see uploading of 
both file?

[Of course, if you use a different method or uploader to make the wheels 
and update to Pypi, then the commands and output will be different.]

Moritz


-- 
Hans Moritz Günther
Massachusetts Institute of Technology
Kavli Institute for Astrophysics and Space Research
77 Massachusetts Avenue
NE83-569
Cambridge, MA 02139
hgunther at mit.edu
https://space.mit.edu/home/guenther/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20220306/94fa302e/attachment-0001.html>