The problem is that in these eggs there are many binary files, as for
example png or sometimes even dlls (sigh), and they are not declared
anywhere in setup.py or Manifest.in.
The best solution would be of course to force everyone to include them
in setup.py, which would make them part of the package when running
egg_info.
This is probably not feasible because:
- they are too many and everywhere
- there is no easy way to detect from the developer if he's including
everything, and the only way would be to see the errors on Hudson
So the only solution left is to:
1. build with bdist_egg
2. copy inside the build egg all the binaries found
any suggestions about how to do that or other ideas?
This procedure should normally be run always on the Hudson server, so I
can make sure for example that there are no artifacts and the directory
tree is always clean..
_______________________________________________
Distutils-SIG maillist - Distut...@python.org
http://mail.python.org/mailman/listinfo/distutils-sig
Suppose for example I need to include a simple png, apparently I have to
do this crazy dance
include_package_data=True,
packages=find_packages(),
package_data={'data': ['xyz.png']},
and even if data/*png is in MANIFEST.in
Isn't there a way to let bdist_egg package also everything found through
the MANIFEST.in?
Suppose for example I need to include a simple png, apparently I have to do this crazy dance
include_package_data=True,
packages=find_packages(),
package_data={'data': ['xyz.png']},
and even if data/*png is in MANIFEST.in
Isn't there a way to let bdist_egg package also everything found through the MANIFEST.in?