health-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Health-dev] Building myGH 2.0.2


From: Axel Braun
Subject: [Health-dev] Building myGH 2.0.2
Date: Tue, 27 Feb 2024 17:32:08 +0100

Hi Luis,

in the list of dependencies, can you check if 
-    'tinycss', 
-    'cssselect'
are still needed?

Next, I came around some config issues.
The packages builds, but may give unexpected results when installing/running....

Cheers
Axel

[    4s]   warning: no files found matching 'doc/images/*.png'
[    4s]   warning: no previously-included files matching '*.pyc' found 
anywhere in distribution
[    4s]   adding license file 'LICENSE'
[    4s]   writing manifest file 'mygnuhealth.egg-info/SOURCES.txt'
[    4s]   
/usr/lib/python3.11/site-packages/setuptools/command/build_py.py:207: _Warning: 
Package 'mygnuhealth.data' is absent from the `packages` configuration.
[    4s]   !!
[    4s]     check.warn(importable)
[    4s]   
/usr/lib/python3.11/site-packages/setuptools/command/build_py.py:207: _Warning: 
Package 'mygnuhealth.images' is absent from the `packages` configuration.
[    4s]   !!
[    4s]     check.warn(importable)
[    4s]   
/usr/lib/python3.11/site-packages/setuptools/command/build_py.py:207: _Warning: 
Package 'mygnuhealth.ui' is absent from the `packages` configuration.
[    4s]   !!
[    4s] 
[    4s]           
********************************************************************************
[    4s]           ############################
[    4s]           # Package would be ignored #
[    4s]           ############################
[    4s]           Python recognizes 'mygnuhealth.ui' as an importable 
package[^1],
[    4s]           but it is absent from setuptools' `packages` configuration.
[    4s] 
[    4s]           This leads to an ambiguous overall configuration. If you 
want to distribute this
[    4s]           package, please make sure that 'mygnuhealth.ui' is 
explicitly added
[    4s]           to the `packages` configuration field.
[    4s] 
[    4s]           Alternatively, you can also rely on setuptools' discovery 
methods
[    4s]           (for example by using 
`find_namespace_packages(...)`/`find_namespace:`
[    4s]           instead of `find_packages(...)`/`find:`).
[    4s] 
[    4s]           You can read more about "package discovery" on setuptools 
documentation page:
[    4s] 
[    4s]           - 
https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
[    4s] 
[    4s]           If you don't want 'mygnuhealth.ui' to be distributed and are
[    4s]           already explicitly excluding 'mygnuhealth.ui' via
[    4s]           `find_namespace_packages(...)/find_namespace` or 
`find_packages(...)/find`,
[    4s]           you can try to use `exclude_package_data`, or 
`include-package-data=False` in
[    4s]           combination with a more fine grained `package-data` 
configuration.
[    4s] 
[    4s]           You can read more about "package data files" on setuptools 
documentation page:
[    4s] 
[    4s]           - 
https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[    4s] 
[    4s] 
[    4s]           [^1]: For Python, any directory (with suitable naming) can 
be imported,
[    4s]                 even if it does not contain any `.py` files.
[    4s]                 On the other hand, currently there is no concept of 
package data
[    4s]                 directory, all directories are treated like packages.
[    4s]           
********************************************************************************
[    4s] 
[    4s]   !!

Attachment: signature.asc
Description: This is a digitally signed message part.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]