1. 23 Sep, 2016 2 commits
  2. 21 Sep, 2016 1 commit
  3. 20 Sep, 2016 2 commits
  4. 02 Sep, 2016 2 commits
  5. 03 Aug, 2016 1 commit
  6. 29 Jul, 2016 1 commit
  7. 25 Jul, 2016 1 commit
  8. 13 Jul, 2016 2 commits
  9. 03 Jul, 2016 1 commit
  10. 30 Jun, 2016 1 commit
  11. 29 Jun, 2016 1 commit
  12. 07 Jun, 2016 1 commit
  13. 06 Jun, 2016 1 commit
  14. 03 Jun, 2016 3 commits
  15. 17 May, 2016 2 commits
  16. 10 May, 2016 1 commit
  17. 05 May, 2016 2 commits
  18. 28 Apr, 2016 1 commit
  19. 01 Apr, 2016 1 commit
  20. 31 Mar, 2016 5 commits
  21. 30 Mar, 2016 1 commit
  22. 07 Mar, 2016 1 commit
  23. 05 Mar, 2016 1 commit
    • Craig Citro's avatar
      Add back the namespace_packages arg in setup.py. · 0e7c0c2f
      Craig Citro authored
      Improves #1296.
      
      The problem: in the previous patch, we tweaked the __init__.py files to use
      namespaces, but no longer declared ourselves as a namespace package. The
      second half was unwise.
      
      Note that this only comes up when installing protobuf alongside another
      package that also installs into the google namespace; as of right now, the
      only PyPI package that does is googleapis-common-protos, though the GAE SDK
      also uses google.appengine. Installing either or both of those alongside this
      package now works.
      
      The case that still remains is the upgrade path, which is also what worried me
      in #713. It seems that if protobuf 2.6.1 is installed, there's no way to
      safely upgrade that to work with a newer protobuf. However, `pip uninstall` &&
      `pip install` does the trick.
      0e7c0c2f
  24. 02 Mar, 2016 2 commits
  25. 19 Feb, 2016 1 commit
  26. 16 Feb, 2016 1 commit
  27. 30 Jan, 2016 1 commit