Confirmed users
513
edits
Auto-tools/Projects/PublicES: Difference between revisions
Jump to navigation
Jump to search
→PyPi and setup.py
Klahnakoski (talk | contribs) No edit summary |
Klahnakoski (talk | contribs) |
||
| Line 181: | Line 181: | ||
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, 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: | ||
The first, and simplest, issue to solve with packaging is to provide a set of pointers to predefined directories. | 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. | ||