4 ms·

Yeah, that moment of panic when you think something Google acquired is something you use.

• tobltobs 10y ago
  In the case of fabric/fabfile this wouldn't matter, as fabric/fabfile looks dead anyway. No Python 3 support, no road map, last Github activity 5 months ago.
  • gdulli 10y ago
    The latest release was last month. Not that it would be concerning if it really was 5 months ago.
    • tobltobs 10y ago
      If I still would be using fabric for deployment I would be concerned.
  • closed 10y ago
    There is a roadmap: http://www.fabfile.org/roadmap.html http://www.fabfile.org/roadmap.html One of the goals in the roadmap is to move part of Fabric's functionality into another library (Invoke), which does have recent activity and supports Python 3.
    • neuronexmachina 10y ago
      Unfortunately, the main dev has been saying that he'll be releasing a rewrite with Python 3 support "at the end of the month" for the past 2-3 years. There's actually a fork ("Fabric3") which fully supports both Python 2.7 and Python 3.4+, but the Fabric dev refuses to merge in any PRs that have been submitted to help with Python 3 support. It's somewhat infuriating. https://github.com/fabric/fabric/pulls?q=is%3Apr+python+3 https://github.com/fabric/fabric/pulls?q=is%3Apr+python+3