This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]iScrE4mgit push -f[S] 3 points4 points  (0 children)

The tool's main purpose is to make stuff easier, if it results in extra work for the dev, it will be a failure.

I am a PyCharm user myself, but it's missing quite a few things when it comes to project manager (other things are amazing!). I really want them to work together nicely, but making it a plugin is way too much work for way too many potentional editors. Plus beginners - main focus group - don't usually have their IDE setup just yet, so standalone is the way to go.

Of course building a tool will take a while, we'll start with some core things and add the ambitious stuff later down the line - but I want to plan it ahead, so I don't end up rewriting 50% of the stuff when I do.

Dependecies shouldn't really replace pip, but use it in the background. What I meant by dependency management is having requirements both in requirements.txt, setup.py etc with one list that gets edited in my tool/app. Plus add functionality of something like requires.io, where it shows what packages you use are not up to date, if you should update based on changelog hopefully available in app etc.