Yes I have sometimes wondered about that. In fact another aspect of npm which I don't get is if you have multiple "instances" of a library (e.g. different versions, or even two copies of the same version) then any…
A caveat of the approach is that you must run the script from the project's folder. This is apparently an unacceptable limitation for some people, judging by the responses to the article - however for others it's not.
But you may want to keep 3 installation levels: global, per-user and per-project. If you use the second to achieve the third, then you no longer have the second.
Actually I don't believe that would happen. I think the relative PYTHONPATH gets expanded at startup and becomes an absolute path. Subsequent changes to the working directory wouldn't affect it.
Yeah I think for me it's more about the intellectual overhead than performance. With this you just have one tool, and it's just easier for me to understand what's going on compared with virtualenv.
Well as we mentioned, it's supposed to solve a situation where you don't want to use all the overhead of virtualenv. The things you care about may be different from what others care about: I'm guessing don't care about…
It doesn't really make much sense to compare xlwings with PyXLL, as they perform a slightly different function and actually could be used together. PyXLL is more comparable to ExcelPython[1], which is open source does a…
Yes I have sometimes wondered about that. In fact another aspect of npm which I don't get is if you have multiple "instances" of a library (e.g. different versions, or even two copies of the same version) then any…
A caveat of the approach is that you must run the script from the project's folder. This is apparently an unacceptable limitation for some people, judging by the responses to the article - however for others it's not.
But you may want to keep 3 installation levels: global, per-user and per-project. If you use the second to achieve the third, then you no longer have the second.
Actually I don't believe that would happen. I think the relative PYTHONPATH gets expanded at startup and becomes an absolute path. Subsequent changes to the working directory wouldn't affect it.
Yeah I think for me it's more about the intellectual overhead than performance. With this you just have one tool, and it's just easier for me to understand what's going on compared with virtualenv.
Well as we mentioned, it's supposed to solve a situation where you don't want to use all the overhead of virtualenv. The things you care about may be different from what others care about: I'm guessing don't care about…
It doesn't really make much sense to compare xlwings with PyXLL, as they perform a slightly different function and actually could be used together. PyXLL is more comparable to ExcelPython[1], which is open source does a…