Merge lp:~jml/udd/less-in-top-level into lp:udd
Proposed by
Jonathan Lange
Status: | Merged |
---|---|
Merged at revision: | 530 |
Proposed branch: | lp:~jml/udd/less-in-top-level |
Merge into: | lp:udd |
Diff against target: |
121 lines (+16/-16) 5 files modified
README (+4/-4) etc-init.d-mass-import (+1/-1) fixit.sh (+2/-2) importer.crontab (+7/-7) pkgimport.conf (+2/-2) |
To merge this branch: | bzr merge lp:~jml/udd/less-in-top-level |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Martin Packman | Approve | ||
Ubuntu Distributed Development Developers | Pending | ||
Review via email: mp+80037@code.launchpad.net |
Description of the change
The top-level of lp:udd is a little bit intimidating. There are a lot of files there, and the beginner will not know which are which. This branch moves all of the scripts to a bin/ directory, and renames them to have dashes instead of underscores and to not have '.py' extensions.
I thought about creating two script directories – one for production scripts and the other for development scripts – but I didn't feel confident enough about the distinction.
Haven't tested this in any way yet. Not exactly sure how, since the most likely issue is PYTHONPATH related.
To post a comment you must log in.
Yeah, the first thing I did after branching lp:udd the other day was look in one of the top level files then close it again and go and find the actual module.
Given my heritage, I dislike the bin/no-extension style but it's clearly the right thing now you've made scripts to run as separate files from python modules.
Having some kind of division between the scripts might be useful (cron vs. manual tool seems relevant) but could be done later anyway.