RFS: wikitrans/1.1-1 [NEW]
Please sponsor the upload of the new package python-uinput * Package name: wikitrans Version : 1.1 Upstream Author : Sergey Poznyakoff * URL : https://puszcza.gnu.org.ua/projects/wikitrans * License : GPL-3+ Programming Lang: Python Description : MediaWiki markup translator This package provides Python framework for translating WikiMedia articles to various formats. The present version supports conversions to plain text, HTML, and Texinfo formats. It builds the following binary packages: python3-wikitrans - MediaWiki markup translator (python3 library) wikitrans - MediaWiki markup translator (utility) The package was checked using the latest version of lintian, and is lintian clean. The package can be found on Git: https://salsa.debian.org/python-team/modules/wikitrans.git -- أحمد المحمودي (Ahmed El-Mahmoudy) Digital design engineer GPG KeyIDs: 4096R/A7EF5671 2048R/EDDDA1B7 GPG Fingerprints: 6E2E E4BB 72E2 F417 D066 6ABF 7B30 B496 A7EF 5761 8206 A196 2084 7E6D 0DF8 B176 BC19 6A94 EDDD A1B7 signature.asc Description: PGP signature
Bug#907337: RFP: python3-dateparser -- Date parsing library designed to parse dates from HTML pages
Package: wnpp Severity: wishlist -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 * Package name: dateparser Version : 0.7.0 Upstream Author : Scrapinghub * URL : https://github.com/scrapinghub/dateparser * License : BSD 3 Clause Programming Lang: python Description : Date parsing library designed to parse dates from HTML pages This is a dependency for webmacs (#907331). I'd rather not get into the python module packaging business, but I guess I will if no-one else takes it up. -BEGIN PGP SIGNATURE- iQGzBAEBCAAdFiEE3VS2dnyDRXKVCQCp8gKXHaSnniwFAluC5dgACgkQ8gKXHaSn niyPVwv7BXH3ZA+/fVyPcOlExaIzbs8bZGrO2XWIGh1WdAaBjDgZTIjr1tsxX9XW 5d6sqkAFR815ZS/U3uR2TrnIXxN6yf4RPPkPSxDRqZCt1XUQ4HaVLONt8VAe2Dwt YO0hw8ccd6Ir1MK4tMSK1weuUym/v0dXrNY98LXWzhXE5L75V2rsrAP7R2qSpDLM Rbr3yAHiTitWLDIIMLRlwW+U1lcY5aEUKGyCDonYsIxEi505aAy7n/g9nFFb6q0i bdij11OZAszrEyAsN+etdVlXwdmREOrE1wgfIndZY09RNFAKQ5k50RyjI2CGZuGW lQQ/Z+KqQx1kbOZVXg6cfNcDJqoZNYvRZAC3NQNSjuHWUt1utN39ovinublr0a7Q w5qgmeef7/NIpLzxbPhYOuX0ESWKsjtuw25NFJKi/azMfCUN+5L/dHQcoysxMd4p sB0/WFoqtrtHBup3hSej6M216XIBTujpxyvPl2cVhgTacRtvwG+yeJU1e/GwaCUq 0ZtBECRc =0ePe -END PGP SIGNATURE-
Dynamic library not found by poretools
Hi, I try to package porechop[1] but somehow it does not find its dynamic library. If I install the resulting package I get: $ porechop could not find cpp_functions.so - please reinstall Any idea what went wrong here? Kind regards Andreas. [1] https://salsa.debian.org/med-team/porechop -- http://fam-tille.de
Re: Dynamic library not found by poretools
On Sun, Aug 26, 2018 at 08:59:21PM +0200, Andreas Tille wrote:
> I try to package porechop[1] but somehow it does not find its dynamic
> library. If I install the resulting package I get:
>
> $ porechop
> could not find cpp_functions.so - please reinstall
SO_FILE = 'cpp_functions.so'
SO_FILE_FULL = os.path.join(os.path.dirname(os.path.realpath(__file__)),
SO_FILE)
if not os.path.isfile(SO_FILE_FULL):
sys.exit('could not find ' + SO_FILE + ' - please reinstall')
As the executable is in /usr/share/porechop and the lib is in
/usr/lib/x86_64-linux-gnu/porechop, this cannot work. The upstream build
system seems to install them into the same directory.
And wtf is -Wl,-soname,porechop/cpp_functions.so?
TARGET = porechop/cpp_functions.so
SONAME = -soname
$(TARGET): $(OBJECTS)
$(CXX) $(FLAGS) $(CXXFLAGS) $(LDFLAGS) -Wl,$(SONAME),$(TARGET) -o
$(TARGET) $(OBJECTS)
It shouldn't have a soname at all, and especially not THIS ONE.
--
WBR, wRAR
signature.asc
Description: PGP signature
Byte-compilation for pypy3
So, I've had some pypy3 packages sitting around for a while, and the
main thing that's stopped me from uploading, is figuring out a plan for
byte-compilation.
If it's sharing /usr/lib/python3/dist-packages with cPython (which it
currently is) then we should figure out a plat for byte-compiling for
it.
rtupdate and postinst / prerm hooks for python3 packages currently call
py3{compile,clean} which only operates on cpython3.
Options I can think of:
1. Ignore byte-compilation entirely.
2. Change py3{compile,clean} to call pypy3{compile,clean} too.
And do some extra compiling / cleaning when pypy3 is installed and
removed.
3. Change py3{compile,clean} to do the work of pypy3{compile,clean} too.
And do some extra compiling / cleaning when pypy3 is installed and
removed.
4. Change the snipets dh_python3 generates, to include
pypy3{compile,clean}, when they exist. And again, do the extra
compiling / cleanup.
5. Something else?
3 *seems* like the right option - py3{compile,clean} supports a range of
cpython versions, already. But I'm not really sure.
Here's what I've got:
https://salsa.debian.org/debian/pypy3
https://people.debian.org/~stefanor/pypy3/
Other TODOs that need some attention but possibly aren't blocking an
upload to unstable:
* test failures and errors
* import paths aren't quite right, yet, e.g.:
- setup.py install installs to a /usr/local path that isn't on
sys.path
- plat-linux2 is on sys.path, but doesn't exist
SR
--
Stefano Rivera
http://tumbleweed.org.za/
+1 415 683 3272
Re: Byte-compilation for pypy3
Unsubscribed
On Mon, Aug 27, 2018 at 10:04 AM Stefano Rivera wrote:
> So, I've had some pypy3 packages sitting around for a while, and the
> main thing that's stopped me from uploading, is figuring out a plan for
> byte-compilation.
>
> If it's sharing /usr/lib/python3/dist-packages with cPython (which it
> currently is) then we should figure out a plat for byte-compiling for
> it.
>
> rtupdate and postinst / prerm hooks for python3 packages currently call
> py3{compile,clean} which only operates on cpython3.
>
> Options I can think of:
> 1. Ignore byte-compilation entirely.
> 2. Change py3{compile,clean} to call pypy3{compile,clean} too.
>And do some extra compiling / cleaning when pypy3 is installed and
>removed.
> 3. Change py3{compile,clean} to do the work of pypy3{compile,clean} too.
>And do some extra compiling / cleaning when pypy3 is installed and
>removed.
> 4. Change the snipets dh_python3 generates, to include
>pypy3{compile,clean}, when they exist. And again, do the extra
>compiling / cleanup.
> 5. Something else?
>
> 3 *seems* like the right option - py3{compile,clean} supports a range of
> cpython versions, already. But I'm not really sure.
>
> Here's what I've got:
> https://salsa.debian.org/debian/pypy3
> https://people.debian.org/~stefanor/pypy3/
>
> Other TODOs that need some attention but possibly aren't blocking an
> upload to unstable:
> * test failures and errors
> * import paths aren't quite right, yet, e.g.:
> - setup.py install installs to a /usr/local path that isn't on
> sys.path
> - plat-linux2 is on sys.path, but doesn't exist
>
> SR
>
> --
> Stefano Rivera
> http://tumbleweed.org.za/
> +1 415 683 3272
>
>
--
Kind regards
滕召智 (Ben teng)
Cell: 13381221392
MSN: free...@hotmail.com
Skype: freet15
Re: Request to join DPMT and PAPT
Hi, čt 23. 8. 2018 v 18:16 odesílatel Nick Morrott napsal: > would like to join the Python Modules (DPMT) and Python Applications > (PAPT) teams, welcome :). -- Best regards Ondřej Nový Email: n...@ondrej.org PGP: 3D98 3C52 EB85 980C 46A5 6090 3573 1255 9D1E 064B
Re: Request to join DPMT and DPAP on Salsa
Hi, po 20. 8. 2018 v 15:25 odesílatel Andrii Senkovych < jolly_ro...@itblog.org.ua> napsal: > Please add me to the DPMT and DPAP teams on Salsa. I am already a team > member and my username is jollyroger-guest. Currently I'd like to > update the python-sqlparse module I maintain. > done. -- Best regards Ondřej Nový Email: n...@ondrej.org PGP: 3D98 3C52 EB85 980C 46A5 6090 3573 1255 9D1E 064B
