Import collective.developermanual from GitHub using File -> Import -> Git and then use Clone button (not Add). collective.developermanual URL is firstname.lastname@example.org:collective/collective.developermanual.git Change protocol to SSH.
Click next next next until you see the project in your Eclipse workspace. Note that EGit puts projects to your home folder, not workspace (slight argh in this point).
Edit some files.
Right click the project to commit.
Then you can right-click to push. This is the tricky part. The dialogue looks like a USS Aircraft Carrier deck control panel. What you need to do is to
In Source ref drop down choose master [branch]
In Destination ref drop down choose master [branch]
Press Add spec button
Then it pops up some dialogs which mean that the push was succesful. Just keep clicking Ok to every window as you won’t understand them in any case.
Every framework define their own email validator, with various regular expressions
Isn’t writing one’s own validation code a bit redundant and exactly “reinventing the wheel” what open source principles so hard try to avoid? Could validation be a low hanging fruit to share among fellow Python projects? As I see it, for the simple data validation, like email and URL, the core code could be easily shared and different Python projects. You basically want just method is_valid_phonenumber(str) and then framework specific way to raise the error to the user.
Do such frameworks already exist? At least I haven’t seen one being used in any big Python project yet 🙁
… or is validation so complex thing, so that validation functions must be tightly integrated with the parent framework and I am missing some big things (like locales, etc.) here?