Ticket #2484 (closed defect: fixed)
Auto-generated files should not be version controled
| Reported by: | bochecha | Owned by: | vinces1979 |
|---|---|---|---|
| Priority: | normal | Milestone: | irrespective |
| Component: | Scheduler | Version: | trunk |
| Severity: | normal | Keywords: | |
| Cc: |
Description
Building an egg of TGScheduler with:
$ python setup.py bdist_egg
I get an egg without most of its metadata: only the SOURCES.txt file is copied inside the egg.
I'm on Windows, so for Windows, tgscheduler.egg-info is the same as TGScheduler.egg-info (when generating the folder).
However, when Python tries to create the actual egg, it sees the difference between lower and upper case, and doesn't include the metadata in the egg.
Sure, a quick fix could be to:
- rename the tgscheduler.egg-info folder to TGScheduler.egg-info
- set name=tgscheduler in the setup.py file.
However, including auto-generated files in version control isgenerally a bad idea, so those files should simply be dropped.
Change History
comment:2 Changed 22 months ago by vinces1979
- Status changed from new to assigned
Good catch sorry I didn't ignore the egg-info, I will clean that up now
comment:3 in reply to: ↑ 1 Changed 22 months ago by vinces1979
Replying to faide:
Vince, it would also be nice if at least me and ChrisA could have access to the pypi entry for TGScheduler.
This would ensure that this important component is always accessible by the TG community even if you drop out of sight.
Sure! not a problem you can usually find me in IRC (vinces) and let me know your pypi usernames
comment:4 Changed 22 months ago by vinces1979
- Status changed from assigned to closed
- Resolution set to fixed
implemented and set to ignore
Vince, it would also be nice if at least me and ChrisA could have access to the pypi entry for TGScheduler.
This would ensure that this important component is always accessible by the TG community even if you drop out of sight.