Auto-tools/Projects/PublicES: Difference between revisions

Jump to navigation Jump to search
Line 180: Line 180:
=== PyPi and setup.py ===
=== PyPi and setup.py ===


Python packaging has not matured to the point where it can handle resource files gracefully.  You can mix your resource files with your code, and they get put into a predictable place, but anywhere else and each Python implementation has it's own idea where your resource file will end up: Making it impossible to know where to find them after installation:
Python packaging has not matured to the point where it can handle resource files gracefully.  You can mix your resource files with your code directories, and they get put into a predictable place, but anywhere else and each Python implementation has it's own idea where your resource file will end up. This makes it impossible to know where to find your files after installation:


The first, and simplest, issue to solve with packaging is to [http://msdn.microsoft.com/en-us/library/system.environment.specialfolder.aspx provide a set of pointers to predefined directories].  With these pointers, placing resources during setup is a much simpler task.
The first, and simplest, issue to solve with packaging is to [http://msdn.microsoft.com/en-us/library/system.environment.specialfolder.aspx provide a set of pointers to predefined directories].  With these pointers, placing resources during setup, and finding them again after, is a much simpler task.
Confirmed users
513

edits

Navigation menu