<p dir="ltr">Hi, some quick thoughts from an add-on developer point of view:</p>
<p dir="ltr">* Pip usage: IMO it's a good idea to use it, and have addons point to its corresponding source (github, pypi, private repo, blender cloud)<br>
* Installation of addons: currently addons are simply stored in a defined path. I always wondered why[1] they are not simply installed in dist-packages, like any other libs. One reason might be that addons would need to use dist-utils, E.g create a setup.py. Allowing to have addons installed like other Python packages might simplify things for the manager and dependencies, but not so for casual scripters. However, probably non-casual scripters won't mind creating a repo like it was a normal Python package<br>
* dependency management: another limitation I find in the current add-on development process is that to include any dependencies the add-on has to include them in the repo itself. Using pip and distutils could help solve this. If I remember correctly, 'requests' was included in blender because many scripts needed it, but of course tat doesn't scale.<br>
* add-on discovery: would be nice to define an official place where addons are distributed from (of it doesn't already exist), like adding a clone of pypi in the blender cloud</p>
<p dir="ltr">Sebastian (from mobile)</p>
<p dir="ltr">[1] besides the fact that all enabled addons need to be imported at startup<br>
</p>
<div class="gmail_quote">On 2 May 2016 8:05 a.m., "Thomas Dinges" <<a href="mailto:blender@dingto.org">blender@dingto.org</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hey,<br>
did you reach out to Addon people already, to get feedback on your<br>
proposal? I mean especially addon developers and users, who use the<br>
Addon UI on a daily basis. Would be good to add them as artist stakeholders.<br>
<br>
Thomas<br>
<br>
Am 30.04.2016 um 02:47 schrieb Peter D. Cassetta:<br>
> Hi all,<br>
><br>
> I just wanted to give a quick first status update. First off, my<br>
> proposal for my Python Package Manager project is now on the wiki:<br>
> <a href="https://wiki.blender.org/index.php/User:PeterCassetta/GSoC_2016/Proposal" rel="noreferrer" target="_blank">https://wiki.blender.org/index.php/User:PeterCassetta/GSoC_2016/Proposal</a><br>
><br>
> Secondly, I talked with my mentor Sybren Stüvel on Tuesday. We discussed<br>
> a couple implementation things, and he recommended I check out the<br>
> Python Package Index, which may be a useful starting point for this project.<br>
><br>
> -Peter Cassetta<br>
><br>
> _______________________________________________<br>
> Soc-2016-dev mailing list<br>
> <a href="mailto:Soc-2016-dev@blender.org">Soc-2016-dev@blender.org</a><br>
> <a href="https://lists.blender.org/mailman/listinfo/soc-2016-dev" rel="noreferrer" target="_blank">https://lists.blender.org/mailman/listinfo/soc-2016-dev</a><br>
><br>
_______________________________________________<br>
Soc-2016-dev mailing list<br>
<a href="mailto:Soc-2016-dev@blender.org">Soc-2016-dev@blender.org</a><br>
<a href="https://lists.blender.org/mailman/listinfo/soc-2016-dev" rel="noreferrer" target="_blank">https://lists.blender.org/mailman/listinfo/soc-2016-dev</a><br>
</blockquote></div>