Admins,
I think it is time to remove SocksiPy. It has many problems, including
a collision with the PySocks slackbuild. PySocks is an updated fork of
SocksiPy. Any users can install PySocks if you need the same or similar
functionality. Additionally, Python already ships with a socks module
if
oups, sorry, thanks Matteo and Ben
On Tue, 30 Oct 2018 10:59:44 -0700
Benjamin Trigona-Harany wrote:
> On 2018-10-30 10:57 a.m., Heinz Wiesinger wrote:
> >
> > We have both python2 and python3 versions of six in a single package in -
> > current and it works just fine. I don't see why the packa
On 2018-10-30 10:57 a.m., Heinz Wiesinger wrote:
We have both python2 and python3 versions of six in a single package in -
current and it works just fine. I don't see why the package would need to be
treated differently from other python libs. What am I missing here?
Grs,
Heinz
I don't think
On Tuesday, 30 October 2018 17:55:59 CET Tim Dickson via SlackBuilds-users
wrote:
> On 29/10/2018 12:44, Rich Shepard wrote:
> > On Mon, 29 Oct 2018, B Watson wrote:
> >> Do we need separate six and python3-six builds?
> >>
> >> Right now, six will build & install python3 support if python3 is
>
On 2018-10-30 10:34 a.m., Matteo Bernardini wrote:
Il giorno mar 30 ott 2018 alle ore 18:31 Frédéric Falsetti
ha scritto:
Hi,
I have qgis3-3.0.0-i586-1_SBo, slackware 14.2
I try to upgrade to qgis 3.4 https://github.com/bosth/qgis3-slackbuild
build fails at QScintilla-qt5 step
g++ -Wl,-O1 -sh
Il giorno mar 30 ott 2018 alle ore 18:31 Frédéric Falsetti
ha scritto:
>
> Hi,
> I have qgis3-3.0.0-i586-1_SBo, slackware 14.2
> I try to upgrade to qgis 3.4 https://github.com/bosth/qgis3-slackbuild
> build fails at QScintilla-qt5 step
>
> g++ -Wl,-O1 -shared -o libqscintillaplugin.so qscintillap
Hi,
I have qgis3-3.0.0-i586-1_SBo, slackware 14.2
I try to upgrade to qgis 3.4 https://github.com/bosth/qgis3-slackbuild
build fails at QScintilla-qt5 step
g++ -Wl,-O1 -shared -o libqscintillaplugin.so qscintillaplugin.o
moc_qscintillaplugin.o -L/tmp/SBo/package-QScintilla-qt5/usr/lib -L/usr/li
On Tue, 30 Oct 2018, Tim Dickson via SlackBuilds-users wrote:
six is a special case, as it is provides compatibility for scripts running
different versions of python. It is useful to be able to create 2 separate
packages though, a python2 version, and a python3 version (with different
package na
On 29/10/2018 12:44, Rich Shepard wrote:
On Mon, 29 Oct 2018, B Watson wrote:
Do we need separate six and python3-six builds?
Right now, six will build & install python3 support if python3 is
installed on the build box. python3-six is identical, except (a) it
requires python3 in the .info fi
