Skip to main content
Pre-release

This release is a pre-release and may not be stable for production use.

Pycsync

Build Status Coverage Status Code Health Dependency Status Pypi Version Pypi Downloads

Sync pictures between filesystem and Flickr

Install

This uses the python_flickr_api.

To install latest:

pip install pycsync

Usage

First oauth needs to be setup for the application:

pycsync -a

Please visit to get an verifier code:
---------------------------------
http://www.flickr.com/services/oauth/authorize?oauth_token=<token>&perms=write
---------------------------------
Please input the verifier code here:

Then copy the link to a browser. After authorizing pycsync, the browser should display something like:

<rsp stat="ok">
  <method>flickr.test.echo</method>
  <api_key>key</api_key>
  <oauth_token>token</oauth_token>
  <oauth_verifier>verifer</oauth_verifier>
</rsp>

Where key is pycsync’s api key, token is the oauth token from above, and verifier is the verifier key for further authentication. Copy the verifier and input it to pycsync.

NOTE: pycsync can either be run from the sync directory or the directory can be specified with the -p option.

Now to sync simply run:

pycsync

Limitations

  1. Flickr stores photos in albums. There is no concept of a sub-album. Thus this requires a flat file structure for the local files. The file system layout must contain one level of directories with files in them. The directories will be mapped to Albums. Any subdirectories will be ignored. Also any top-level files will be ignored.

Metadata

Release files for pycsync 0.1b1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for pycsync 0.1b1
File Size Uploaded Provenance Actions
pycsync-0.1b1.tar.gz 5.5 kB Without provenance Details for pycsync-0.1b1.tar.gz

Release files / pycsync-0.1b1.tar.gz

Download URL pycsync-0.1b1.tar.gz
Size 5.5 kB
Tags Source
SHA-256 checksum
How to use checksums
9e4cb0fc98901ca96130aea2b97db30c814dcb179ef5ea18e545958f7070aab7
BLAKE2b-256 checksum
How to use checksums
0edb4e2a221c0dcdf3043ce44fa3a293eb092266fbdd203a8e52d7dc97e79436
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No

Security for pycsync 0.1b1

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page