I generally work fast and careful, and the docs are lacking on how to
find dependencies (unless I am missing it). As noted previously though
there are a large number of things outdated, so of course submissions
will be in batches, not sure how you expect this worked around. If there
is a module I use, or am just working to update in the tree, and the
dependencies are outdated I will send those at the same time as its
required.
I was not requesting they immediately be pushed to the tree without
review but there is also a lack of feedback for me to know what changes
are needed to improve my porting and make it easier for you guys going
forward.
Edward Lopez-Acosta
On 11/20/18 5:39 PM, Stuart Henderson wrote:
On 2018/11/20 17:11, Edward Lopez-Acosta wrote:
Stuart,
I did some thinking on this as a heavy consumer, and light developer, of
Python applications.
There are 455 Python3 modules currently in the repository would would be
unreasonable to test all of them [1].
Yes it would be unreasonable to do runtime testing on all of them. But
they are going to need REVISION bumped on the whole lot of them for a
python version switch and at least build testing is needed to make
sure we don't break the ports tree.
That being said there also appears to
be hesitation on importing updated modules by the OpenBSD team [2].
You send diffs for a stack of updates in one go, are missing finding
dependencies in some cases, and are giving the impression of working fast
(which is not *necessarily* a problem but might be - we don't really
know you / your work and whether it's fast+careful or just fast).
So yes there is hesitation to just pushing these to the tree without
further thought and tests.