The problem with this change is that it would change the method behavior and break compatibility. I'm not yet sure how this could be properly handled.

I know, it was just my suggestion; your API (for which I thank you btw, it's pretty awesome) is structured similar to GL's own, so logically speaking me personally expected the archive() function to be just that already.
We have one luck though; the function won't accidentally archive your project while args are passed to it, it'll bork with a TypeError.
OTOH you might do a archive('yes-i-really-really-mean-it') kind of construct.

The way I see it you could do:

• don't change the function, make the new one i.e. project_archive() or something
• if archive() was called without sha or kwargs it behaves like project_archive()
  (I think this one will trip over people, just throwing it out there as a possibility)
• Write a note in the log that you're going to depreceate the 'old' archive(sha=None, **kwargs) in favour of repo.archive(sha=None, **kwargs) and after a while do the change

I've implemented archive support in the archive_() and unarchive_() methods. This is not very nice but I wasn't yet ready to change the behavior of archive().

The method are explicitly listed in http://python-gitlab.readthedocs.io/en/latest/gl_objects/projects.html

I'll remove the archive() method at some point, then rename the new methods.

Thanks for your suggestions BTW :)

Tnx 4 the feature :) sorry I didn't respond earlier there.