Adding support for Python 2.6

Moin

Find the patch attached.

I have not yet looked how I can push this patch directly to GitHub. Perhaps
somebody would be so kind to point me to a guide?

Let me see, perhaps I already got this right. I had a look at Geoffs Git
activities (see “qit-questions.png”).

Geoff has his own tree of Avogadro. Only he commits there. Marcus has his
tree, but his tree is at the same time the equivalent to svn-trunk for all of
us. Same as Linus Torvalds tree. There is no technical reason, we just all
agree that Marcus’ tree is our baseline.

Marcus and Albert commited two commites each. 8 ours ago Geoff sucked
in “pushed to master” those four patches and commited them to his tree. After
this push, Geoffs and Marcus’ tree are in sync again.

If Geoff wants to commit he does so in HIS tree. Marcus then pushes Geoffs
tree into his tree when he wants to. That was done in the commit 2df49f96
(Merge commit ‘ghutchis/master’ )

Is that correct so far?

If so I need to clone (is that the right lingo) Marcus’ tree and push to
GitHub. Then Marcus sucks in my patches into his tree?

Carsten

“…[Linux’s] capacity to talk via any medium except smoke signals.”
(By Dr. Greg Wettstein, Roger Maris Cancer Center)

Hi Carsten,

Carsten Niehaus wrote:

Moin

Find the patch attached.

I have not yet looked how I can push this patch directly to GitHub. Perhaps
somebody would be so kind to point me to a guide?

I wrote such a guide, this should hopefully help people get up to speed
quickly. If there are any mistakes in the guide please let me know (or
correct it on the wiki). Please see

http://avogadro.openmolecules.net/wiki/Working_With_Git

Basically, GitHub - cryos/avogadro: Avogadro 1 is not under active development, the repository was archived in September 2021. Development of Avogadro 2 is being done at https://github.com/openchemistry/avogadrolibs. Avogadro is an advanced molecular editor designed for cross-platform use in computational chemistry, molecular modeling, bioinformatics, materials science, and related areas. acts as the central repo
which all other repos are forked from. When I see changes in other forks
I can merge them into master. Everyone should be syncing with this
master and generally not with any other masters.

If you still have questions after reading the guide I wrote please let
me know and I will see if I can fill in any remaining blanks.

Thanks,

Marcus