Hot answers tagged

1

Don't think too much about Pip. If your Setuptools configuration works correctly, it's easy enough to upload all and only those files you actually want to PyPI (at which point end users will be able to install it with Pip; developers will be cloning your git repository since they need history for things like git bisect to work, and Pip does not provide git ...


1

I'm not necessarily saying you shouldn't host your company's repository in the cloud, but I've personally experienced some disadvantages and pain with cloud hosting. How fast and reliable is your internet connection? To me, that is the single biggest consideration. For example, my company is located in a pretty rural area. While our intra-net speeds are ...


1

It sounds like you're missing branches (or rather 'tags' or 'release' branches). Instead of using your SVN revnum as a reference to determine which version you're installing, you should create a branch at that released revision. You then deploy that branch name. It makes it easier to branch even if there are no changes so every module keeps the same ...


1

I think you have a lot of good ideas already, I've used most of them on various projects throughout the years, and your primary concern seem to be the inability to tell what version of all modules where included in a given package if you split them up. I'm all for splitting them up, at some level of granularity, especially if you have multiple teams and ...



Only top voted, non community-wiki answers of a minimum length are eligible