Re: python / python3 3 pybuild and bin script

y documented (see: #71621). I never try to use this system since I am not very confortable with it. > > Thoughts anyone? What would you consider best practice? Yes opinions of other would be interesing. See you Fred -- GPG public key 4096R/4696E015 2011-02-14 fingerprint = E92E 7E6E 9

Re: python / python3 3 pybuild and bin script

and this is why I propose to use spyder3 instead of spyder, to be clear that the stability is not of the same level for now. Cheers Frederic -- GPG public key 4096R/4696E015 2011-02-14 fingerprint = E92E 7E6E 9E9D A6B1 AA31 39DC 5632 906F 4696 E015 uid Picca Frédéric-Emmanuel GPG pu

Re: pybuild sphinxdoc and extensions

build time (of the documetnation). So it needs to find also the Extensions. This is why I try to set the proper PYTHONPATH during the doc generation. A+ Fred -- GPG public key 4096R/4696E015 2011-02-14 fingerprint = E92E 7E6E 9E9D A6B1 AA31 39DC 5632 906F 4696 E015 uid Picca Frédéric-Emmanue

Request to join the team

Hello, my name is Picca Frédéric-Emmanuel (picca), I would like to join the python-modules team in order to package python-qtconsole for the ipython transition. Which I hope could be done for strech. so I plan now to add all my new python module packages into python-modules. my allioth

where should we put private libraries

Hello, I am working on the dials[1] package. This scientific software produce a bunch of python extension via boost python, but also a bunch of libraries, which are the common part of the python extension. when I package it, I moved the common library under the /usr/lib// directory. This way the

wheel and pip with setuptools

Hello, I try to fix an FTBFS in the python-xrayutilities package. When I try to build it, I get this error message., I do not understand why I need to add a build dependency to python3-wheel.Is it something missing in the dependency of python3-setuptools or python3.10 ? thanks for your help F

Re: wheel and pip with setuptools

Le 2022-10-30 00:39, Scott Kitterman a écrit : Adding pybuild-plugin-pyproject to build-depends should solve it. It looks like it is trying to do the new pyproject.toml style build without all the necessary parts in place. the package contain a pyproject.toml file and a setup.py one. the bu

change in the extention importation with 3.11

Hello, I am trying to fix this bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024859 I find the error message not very informative... :~/$ python3.11 Python 3.11.0+ (main, Nov 4 2022, 09:23:33) [GCC 12.2.0] on linux Type "help", "copyright", "credits" or "license" for more information.

pybuild autopkgtest

Hello, Is it possible instead of using pybuild-plugin-autopkgtest during the build, to call the same logic from d/t/control. something like Test-Command: pybuild-autopkgtest-run This way it would be possible to deal with the Dependencies on our own and avoid the problem of missing dependencies

module name conflict

Hello I would like to package this piece of software: http://www.tango-controls.org/static/tau/latest/doc/html/index.html So it provides a tau python module. but the debian python-tau also provides a tau module. I already propose to the upstream to change the name of the module http://sourcefo

python module name conflict

Hello I would like to package this piece of software: http://www.tango-controls.org/static/tau/latest/doc/html/index.html which provides a tau python module. but the debian python-tau also provides this tau module. I already propose to the upstream to change the name of the module http://sourc

RE : python module name conflict

> Hi Frédéric, Hello > IMHO one of them needs to be renamed, probably the newest one. If the one you > want to package is only used in the project upstream mentions, renaming that > one > would be a good option They can temporarily do something like this: > try: >import newname > except Imp

RE : RE : python module name conflict

> You put the module in some dir and then use a .pth so you can import it > normally. This will avoid the file conflict, but not the namespace one, and > I'm > not sure what would happen if you install both modules, so you better prod > upstream into renaming it. > Cheers, > Emilio thanks, I wil

package providing an ipython Extension

Extensions So is it enought to install the ipy_profile_tango.py at that place during the build phase of the package ? thanks Frederic -- GPG public key 1024D/A59B1171 2009-08-11 fingerprint = 1688 A3D6 F0BD E4DF 2E6B 06AA B6A9 BA6A A59B 1171 uid Picca Frédéric-Emmanuel sig

Re: package providing an ipython Extension

blic key 1024D/A59B1171 2009-08-11 fingerprint = 1688 A3D6 F0BD E4DF 2E6B 06AA B6A9 BA6A A59B 1171 uid Picca Frédéric-Emmanuel signature.asc Description: PGP signature

Re: package providing an ipython Extension

Le Mon, 09 Aug 2010 16:57:30 +0200, Bernd Zeimetz a écrit : > On 08/09/2010 04:10 PM, Picca Frédéric-Emmanuel wrote: > > > I am using python-support but I am not sure I understood what is the > > relation of my > > problem with the section you pointed me in the pyth

Re: Compressing objects.inv?

0ef [2] http://lists.debian.org/20101108231614.gu12...@onerussian.com See you Frederic -- GPG public key 1024D/A59B1171 2009-08-11 fingerprint = 1688 A3D6 F0BD E4DF 2E6B 06AA B6A9 BA6A A59B 1171 uid Picca Frédéric-Emmanuel signature.asc Description: PGP signature

sphinx and intersphinx doc generation.

create a python--doc package and make it depends on the other right python--doc. Is this problem similar to the doc generated by javadoc for the java packages. thanks for your attention. Frederic -- GPG public key 1024D/A59B1171 2009-08-11 fingerprint = 1688 A3D6 F0BD E4DF 2E6B 06A

Re: sphinx and intersphinx doc generation.

Le Mon, 14 Feb 2011 16:48:40 +0100, Jakub Wilk a écrit : > * Picca Frédéric-Emmanuel , > 2011-02-14, 14:55: > >MainThread INFO 2011-02-14 12:54:51,927 root: Generating grammar > >tables from /usr/lib/pymodules/python2.6/sphinx/pycode/Grammar.txt > >MainThread

debuging a sip4 generated binding

Hello, I am working on a packqge which use PyQt4, but When I try to test it I got this error message. picca@grisette:~/Debian/taurus$ taurusform python: /build/buildd-sip4-qt3_4.10.2-1-i386-SoYLd5/sip4-qt3-4.10.2/siplib/siplib.c :2600 : sip_api_parse_result: L'assertion « assign_h

Re: debuging a sip4 generated binding

Le Mon, 14 Feb 2011 17:40:59 +0100, Picca Frédéric-Emmanuel a écrit : > Hello, > I am working on a packqge which use PyQt4, but When I try to test it > I got this error message. > > picca@grisette:~/Debian/taurus$ taurusform > python: > /build/buildd-sip4-qt3_4.10.2-1

Re: debuging a sip4 generated binding

696E015 2011-02-14 fingerprint = E92E 7E6E 9E9D A6B1 AA31 39DC 5632 906F 4696 E015 uid Picca Frédéric-Emmanuel signature.asc Description: PGP signature

Re: Broken search in Sphinx-generated documentation

Should we add a Build-Dep: python-sphinx (>= 1.0.7-4) for all thoses packages ? thanks Frédéric -- GPG public key 4096R/4696E015 2011-02-14 fingerprint = E92E 7E6E 9E9D A6B1 AA31 39DC 5632 906F 4696 E015 uid Picca Frédéric-Emmanuel GPG public key 1024D/A59B1171 2009-08-11 finge

RE : Bits from the Sphinx maintainer

> In python-sphinx 1.0.7+dfsg-1 I made a few important changes: > 3) There is a new helper tool, dh_sphinxdoc, which helps with packaging > Sphinx-generated documentation. More specifically: > - it does a few sanity checks (e.g. for missing files that are > needed for the JavaScript to work); > -

RE : RE : Bits from the Sphinx maintainer

> This is pretty weird place for documentation. dh_sphinxdoc by default > looks only into subdirectories of /usr/share/doc/, but you can tell it > to look somewhere else. I tryed but then comes the problem presented in the previous mail dh_sphinxdoc is executed before dh_python2. Maybe we should

pyqwt5 package

Hello, It seems that the migration into Testing of pyqwt5 is blocked by an RC bug. Indeed it block also the migration of a few other packages. at least pymca guiqwt pyacidobasic (in a few days) epigrass Reading the bugs threads [1]. all problem seems solved. so my question is : did I miss someth

RE : PyCon 2013 -- anyone going? ideas for the talks?

hello, in that case you should have a look to the pythonxy project http://code.google.com/p/pythonxy/ this pylab distribution is quite similar cheers Fred De : Thomas Kluyver [tho...@kluyver.me.uk] Date d'envoi : vendredi 21 septembre 2012 19:24 À : py

RE : On robustness of maintainer scripts

Hello Jackub > prerm > = > ... > Real-world failure: #706758 should I reassign this bug to python ? If I understand well, all this, python should be fixed then a rebuild of all python packages should be done. right ? which bug of python should I track to know when a rebuild of the packag

RE : python3.3 status

pytango - Shouldn't have been removed, FTBFS on s390 - #711761 This bug was forwarded to the upstream. -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/a2a20ec3b8560d4

RE : python3.3 status

>Looking at where we are now, the open issues are down to #711761 and #711761. To my opinion, (I am the maintainer of pytango) this is not a problem if pytango is not available on s390. I forwarded the bug to the upstream with a patch, I am waiting for the approval of the upstream. Nevertheless

problem with python-qt4 and python-qwt5-qt4

Hello, I am working on this bug [1] , after some investigration it seems that this is a problem of incompatibility between python-qwt5 and python-qt4. I do not know what is the best way to solve this issue. rebuild python-qwt5-qt4 but python-qt4 should be fixed also to set the right Breaks.

python / python3 3 pybuild and bin script

Hello, I am packaging the next version of spyder which is a python IDE. The next version will support python3 so I need to add a spyder3 binary package which will contain /usr/bin/spyder3 the upstream script only create /usr/bin/spyder during the build So my question is do we have something in

update of rope

Hello, I would like to update the current rope package 0.9.2 -> 0.9.4 and refresh the packaging using pybuild because the ropemacs mode doesn not work properly with 0.9.2., but seems to work fluently with 0.9.4 now, I can not afford to learn svn-buildpackage. days are too short... I use only gi

RE:update of rope

> You might want to harvest hints given in [0] which hopefully allow you > to keep gbp and use git-svn. > Hope this helps. I will have a look, thanks for the link Cheers Frederic -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Conta

pybuild sphinxdoc and extensions

Hello I try to find a way to teach my rules files how to generate the documentation using pybuild I found the classique override_dh_auto_build-indep: dh_auto_build PYTHONPATH=. http_proxy='localhost' sphinx-build -N -bhtml doc/source build/html # HTML generator but is does n

RE:pybuild sphinxdoc and extensions

> Yes. Which wiki page? URL? this one [1] > Ahum... "maintaining a patch" is probably an overstatement here. > Here's an example "diff" (not a valid diff for computers, but enough for > understanding by humans): > extensions = ['sphinx.ext.autodoc', > 'sphinx.ext.todo', >

RE:git-dpm vs gbp-pq: new upstream and patch refresh (long)

> > The file is patched, but now I have an d/p/0005- file instead of a > > modified > > 0003- patch file. Sigh. In this case you can use git rebase -i master edit the commit to merge 0003- and 0005- Cheers Frederic -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a s

package with multiple modules name spaces

Hello, I am working on a source package pymca, which will provide 2 modules PyMca5 and fisx now following the policy I must name the binary package this way python-pymca5 python3-pymca5 python-fisx python3-fisx The previous package provided only one module, so I should use the minimalist dh

RE:package with multiple modules name spaces

Hello, thanks for your reply > you can > 1) invoke dh twice with different set of options (if these modules >are in two different directories or use two different setup.py >files/options) the use the same setup.py for now... > or > 2) (ab)use --ext-dest-dir/--ext-pattern to move some fil

trying to solve the pytango FTBFS with gcc5

Hello, guyes, I am working on this bug report[1], and I would like your opinion. this package depends on the tango library which was rebuilt with gcc5 and updated for the libstdc++6 transition. Now as you can see in the bug report, pytango FTBFS with a missing symbol. and indeed the missing symb

RE:trying to solve the pytango FTBFS with gcc5

> The actual error is about another symbol: > _PyTango.so: undefined symbol: _ZN5Tango17ranges_type2constIjE3strE > This symbol is old ABI, as opposed to > _ZN5Tango17ranges_type2constIjE3strB5cxx11E > (which *does* exist in libtango.so.8). > Can it be a bug in GCC? I don't think it should pro

RE:trying to solve the pytango FTBFS with gcc5

> I have created a small test project (attached) that has a library exporting > "std::string Tango::ranges_type2const::str" symbol and a test program > using it. thanks a lot. now we can see if gcc and g++ generate different symbols. > Interestingly, GCC uses the symbol _ZN5Tango17ranges_type2c

RE:trying to solve the pytango FTBFS with gcc5

> I have created a small test project (attached) that has a library exporting > "std::string Tango::ranges_type2const::str" symbol and a test program > using it. > Interestingly, GCC uses the symbol _ZN5Tango17ranges_type2constIjE3strE > (*without* the B5cxx11 part) for both library and client. Y

RE:pypi2debian

Hello, just for information what is the difference with pypi-install from the pyton-stdeb package

Status of ipython-qtconsole

Hello, I saw that a bunch of jupyter projects were uploaded into experimental. It would be nice to have also the qtconsole part. I would like to know if there is already an effort in order to package the current ipython-qtconsole. I would be glade to help package this module. One of my package

Request to join the team

Hello, I did a request from the alioth website yesterday, in order to maintain python-qtconsole inside the python-modules repository. So this is just a ping directly from the mailing list. thanks Frederic

RE:Request to join the team

> that's because alioth interface is ignored. Unfortunately I don't know > how to disable it and people who didn't read our policy still use it. Sorry. I plan to read your policy in order to achieve my package, but I am used to the alioth request button :)) Cheers Frederic

RE:Status of ipython-qtconsole

Hello Julien > Not as far as I know. I'd be happy to review a package if that would > help. I just pushed here my wip package git clone git+ssh://git.debian.org/git/python-modules/packages/python-qtconsole.git I have debian/TODO.org file where I put the remaining things to do. I would be gla

RE:Status of ipython-qtconsole

> I think in jupyter this is meant to be handled by the --kernel option - ie > jupyter qtconsole --kernel python2 ok it works >jupyter qtconsole --kernel python3 $ jupyter qtconsole --kernel python3 Traceback (most recent call last): File "/usr/bin/jupyter-qtconsole", line 9, in

Packaging pytango 9.2.0

Hello Guyes, I am working with Sandor (CC) in order to upgrade the pytango package. With this new version, the upstream decided to rename the module from PyTango to tango import PyTango -> import tango The previous package provided these binary packages python-pytango python3-pytango now it s

how to build sphinx doc when there is extension

Hello I am using this snipset when I want to build the sphinx documentation for all python available. (this is a sort of unit test). Usually the sphinx doc use auto-doc and then it allows to check that all modules can be imported. override_dh_sphinxdoc: ifeq (,$(findstring nodocs, $(DEB_BUILD_

RE:Packaging pytango 9.2.0

Here for itango Build-Depends: debhelper (>= 9), dh-python, python-all-dev, python-setuptools, python-tango, python3-all-dev, python3-setuptools, python3-tango Package: python3-itango Architec

RE:how to build sphinx doc when there is extension

> how about doing it outside pybuild? Do you really need to build it for > each interpreter / version? It is a sort of unit test during the build that auto-doc works for all versions of the interpreter. th eunit test is try to import all the modules provided by a packages. Is there something w

RE:how to build sphinx doc when there is extension

Hello > I agree with Ben that you shouldn’t really be using Sphinx for testing > your source. ok but thanks to this I found some missing binary dependencies during the build process... so it increased the quality of my packages. Even if I would prefer a complet unit test suite... I could put th

RE:Plan for ipython 5 transition

Great, +1 for this long awaited migration :)) here the maintainer of lmfit-py, sardana ans spyder I will take care of lmfit-py. but I think that the notebook is not a strong constrain for lmfit-py I did the work for sardana., so it is ok in experimental I did the work with others for spyder an

building manpages via setup.py

Hello, I am working on the pyfai package. This pacakge contain one module with extensions (the important point) The new upstream version 0.14.0 provide a build_man target via the setup.py So in ordert to generate the doc I need to do python setup.py build_man Now if I look at this target, I ca

RE:building manpages via setup.py

> Simplest I can think of would be to build the extensions inplace > followed by the call to build_man. Something like: > override_dh_auto_build: > dh_auto_build > python3 setup.py build_ext --inplace > python3 setup.py build_man I do not want to build once more the ext (i

RE:building manpages via setup.py

Hello piotr > if you want to test all requested Python interpreters: I prefer this solution in order to check that the built extensions are working for all the python interpreters. The doc use autodoc so it is nice to have this functionnality | override_dh_auto_build: | dh_auto_build -- -

RE:building manpages via setup.py

> export PYBUILD_AFTER_BUILD={interpreter} setup.py build_man Thanks, The only drawback I see with this solution is that I want to run dh_auto_build 2 times, - 1 for the arch part (pyhon modules, extensions and manpages) - 2 for the indep part (doc build) nevertheless thans a lot it is flexxib

RE:building manpages via setup.py

> Perhaps the LibraryStyleGuide should be updated to reflect on this > change? I believe we are still advising explicit http_proxy / > https_proxy exports prior to running sphinx-build. And running sphinx-build does not work expecially if there is extensions in the documentation. sphinx-build sho

RE:building manpages via setup.py

> At the end of the day, it is just a matter of providing an appropriate > PYTHONPATH, regardless of whether pybuild is used or not. Yes but to avoid the multiplications of way to provide this PYTHONPATH. Is it possible to have the recommended way which works for modules and extensions. once ag

RE:building manpages via setup.py

> PYTHONPATH=. sphinx-build -N -b html > One can also use the sphinx-generated Makefile if available: > PYTHONPATH=$(CURDIR) $(MAKE) -C html > Both are simple one-liners and do not rely on pybuild. Yes it works but this is fragile since the organisation of the module can change in the sourc

RE:building manpages via setup.py

> First, that's very speculative. Second, that's upstream's problem. > The upstream Makefile and conf.py are likely generated by Sphinx itself > via sphinx-quickstart. Did your upstream tinker with them that much that > they cannot be trusted? No this is just that does not fit well with extension

RE:building manpages via setup.py

> The snippet you quoted is not specific to extension modules but to the > use of the autodoc feature, which requires the modules to be in the > PYTHONPATH. The `sys.path.insert` hack is just here so that you don't > have to specify PYTHONPATH yourself when running the upstream Makefile. I just sa

RE:building manpages via setup.py

y: # clean up the script if script_name is not None: os.remove(script_name) When I run the build it generate a pydistconfig file wit this content D: pybuild plugin_distutils:55: pydistutils config file: [clean] all=1 [build] build-lib=/home/picca/Debian/silx/s

RE:building manpages via setup.py

False, configure_args=None, configure_only=False, custom_tests=False, destdir='debian/tmp', detect_only=False, dir='/home/picca/Debian/silx/silx', disable=None, ext_destdir=None, ext_pattern='\\.so(\\.[^/]*)?$', install_args=None, install_dir=None, install_only=False,

RE:building manpages via setup.py

Ok, If I replace '{interpreter} setup.py build_man' by 'env; setup.py build_man' I get this HOME=/home/picca PYTHONPATH=/home/picca/Debian/silx/silx/.pybuild/pythonX.Y_2.7/build but If I read the code of def create_pydistutils_cfg(func): """distu

502 Bad Gateway with the pipy redirector ?

Hello, When I tries to update one of my package, I got this errro via uscan :~/Debian/lmfit-py/lmfit-py$ uscan uscan warn: In watchfile debian/watch, reading webpage https://pypi.debian.net/lmfit/ failed: 502 Bad Gateway Someone knowns what is going on ? Cheers Frederic

Disabling test does not work, is it a pybuild bug ?

Hello before reporting a bug against dh-python, I would like your opinion, I try to skip test for all the debug version of the interpreter. So I add this in the rules files export PYBUILD_DISABLE_python2-dbg=test export PYBUILD_DISABLE_python3-dbg=test and here is my test target # WITH_QT_TES

pydist and install_requires

Hello, still working on my silx package... When it comes to python:Depends, I try to add the right entries in the setup.py So I added a bunch of modules there. -"setuptools"] +"setuptools", +# Debian added +"ipython", +"qtconsole", +"enum34", +

RE:pydist and install_requires

Hello Andrey > Isn't just adding the package names to Depends easier? I just want this to be automatically generated and "upstreamable". > So do you have python-opengl, python-pyqt5 etc in Build-Depends? yes, I think that I found the problem for opengl. the egg info gives the name of the projec

RE:pydist and install_requires

Hello Ghislain > Indeed, you need to use the name registered on pypi, which can be > different from the Debian package name. For OpenGL, the project is > registered as PyOpenGL, for PyQt5 the name is PyQt5. yes it works :) > but for pyqt5 I do not have egg informations. Maybe the solution would

-dbg packages and dependencies

Hello, it seems that dependencies are not generated for the -dbg packages by dh_python[23] Is there s way to ask dh_python to generate these dependencies from the build-dep of a package. Thanks Frederic

RE:providing sphinx3-* binaries

Hello guyes. > override_dh_sphinxdoc: > ifeq (,$(findstring nodocs, $(DEB_BUILD_OPTIONS))) nodocs or nodoc I alsa do something like this when there is extensions. override_dh_sphinxdoc: ifeq (,$(findstring nodoc, $(DEB_BUILD_OPTIONS))) PYBUILD_SYSTEM=

RE:providing sphinx3-* binaries

Or just use the sphinx-generated Makefile if there is one: Except that when there is an autodoc in the documentation, I like to build the doc with all {interpreters}. It is a sort of unit test Cheers Fred

RE:Python2 EOL and moving towards Python3

what about, packages which contain in the rules files direct call to dh_numpy2 ? cheers Frederic

RE:packages that use dh_python{2,3} but don't depend on dh-python

What about teaching cme how to fix packages build-depends. this way a simple cme fix dpkg would do the job ?

how to deal with py-file-not-bytecompiled

Hello, I am preparing the new silx package and I got these error messages from adequate This package produce the silx python module but install also a bunch of files for qtdesigner in the rules file with this command. # install the qtdesigner files only for the python3 package d

RE:how to deal with py-file-not-bytecompiled

thanks a lot

RE:how to deal with py-file-not-bytecompiled

> A bit off-topic, but you should not use Qt 4 in new packages. > See https://lists.debian.org/debian-devel-announce/2017/08/msg6.html. I did the migration to qtcreator :)) do not worry Fred

Is there a tool to debianize for the first time a package from pypi

Hello, I need to create a new package for spyder_kernels. Is there a tool which allows to create the first version of a package which create the debian/directory from the setup.py files ? thanks Frederic

RE:Is there a tool to debianize for the first time a package from pypi

no problem Ghislain, I am on it :)) Cheers Fred

RE:Is there a tool to debianize for the first time a package from pypi

Hello, once debianize, is there a command which allow to update the control file for a new upsteam version in order to take into account the new python dependencies ? It would simplify a lot the maintenance of python packages. py2dsp update like the cme command ? Cheers Frederic

RE:Is there a tool to debianize for the first time a package from pypi

> remove control file and invoke py2dsp - it will regenerate it > That said, you probably want dch (debchange) rather than new control > file Thanks a lot, It would be nice to have an equivalent of dgit-main-xxx for maintaining python packages. Maybe in the policy ? this way peoples new commer

pybuild and pytest.

Hello, I am trying to upgrade spyder and activate the unti test during the build. But when pybuild try the test it ends with this error message dh_auto_test: pybuild --test --test-pytest -i python{version} -p "3.7 3.6" returned exit code 13 With no other information. So My question is how ca

python3.7-dbg issue ?

Hello, I try to understand this [1] test failure with python3.7-dbg so, I ran this on my unstable box and I got this error from within gdb testTrainingSpectrumReading (specfilewrapperTest.testSpecfilewrapper) ... ok -- Ran 43 t

RE:python3.7-dbg issue ?

Ok, I could simplify the problem to a single import picca@mordor:~$ python3.7-dbg Python 3.7.0+ (default, Aug 31 2018, 23:21:37) [GCC 8.2.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import silx.opencl /us

RE:python3.7-dbg issue ?

tWarning) * ob object : type: tuple refcount: 0 address : 0xb5f507a4 * op->_ob_prev->_ob_next object : Erreur de segmentation picca@mordor:~$ python3.7 -c "import pyopencl" maybe the problem is in pyopencl. But I find really strange thaht I have the WArning messages with python3.7-dbg but not with python3.7 Is it normal ?

RE:python3.7-dbg issue ?

Hello, I rebuilt pyopencl,and the problem vanished. so what should I do now ? ask for a binNMU or try to understand what is going on ? thanks for your time. Fred picca@mordor:/tmp$ python3.7-dbg -c "import pyopencl" /usr/lib/python3/dist-packages/pkg_resources/_vendor/pypars

cffi issue ? was RE:python3.7-dbg issue ?

I think that there is a problem with cffi pyopencl was built with python3-cffi-backend i386 1.11.5-1 [80.2 kB] but the backend used for the test is the current 1.11.5-3. here the Debian changelog python-cffi (1.11.5-3) unstable; urgency=medium [ Ondřej Nový ] * Use 'python3 -m sphinx

RE:TypeError: ord() expected a character, but string of length 3 found (Was: Updated python-uncertainties)

Hello Andreas, during the test does it load the moduels from the source files or does it use the one under the build directory. Maybe there is a missmatch between python2 code and 2to3 python code targeting python3. did it helped ? Fred

RE:TypeError: ord() expected a character, but string of length 3 found (Was: Updated python-uncertainties)

Hello Andreas, it seems to me that the problem is due to the 2to3 conversion. I looked at the first failure when you re-activate the unit test[1] to my opinion, the code is modify in place with 2to3. So the code on the source after the configuration is already converted to python3. And during t

RE:TypeError: ord() expected a character, but string of length 3 found (Was: Updated python-uncertainties)

You are right , I did not noticed, that setuptools was not part of the build dependencies...

RE:TypeError: ord() expected a character, but string of length 3 found (Was: Updated python-uncertainties)

> try adding python3-setuptools to Build-Depends ok I removed all the black magic from the debian/rules and added setuptools :) so now, I have this error when building the documentation PYTHONPATH=`pybuild --print build_dir --interpreter python3` http_proxy='http://127.0.0.1:9/' sphinx-build -N

RE:TypeError: ord() expected a character, but string of length 3 found (Was: Updated python-uncertainties)

Now the test part :)) Correlated variables. ... ok Tests the input of correlated value. ... ok == ERROR: Failure: ImportError (No module named tests.support) --

RE:TypeError: ord() expected a character, but string of length 3 found (Was: Updated python-uncertainties)

I found the culprite, the conf.py file of the documentations prepend ".." to sys.path befor importing the module. This is why it use the wrong version of the built module. Now during the build I have this D: dh_python3 dh_python3:164: args: [] D: dh_python3 dh_python3:166: supported Python vers

RE:TypeError: ord() expected a character, but string of length 3 found (Was: Updated python-uncertainties)

I found in the code a string with a ur'' This is the problematic line. I do not know if this is a valid string construction. I also dound that you need to remove the sys.path modifications from the conf.py. this can cause some troubles during the build. Cheers. Fred

RE:TypeError: ord() expected a character, but string of length 3 found (Was: Updated python-uncertainties)

I think that the real problem with the current build is that the conf.py file change the sys.path. this is why we see this syntax eror. sphinx pick the wrong path. I can not work on this now..., I am not in fron of a Debian box nor have access to one todays... Cheers Fred

RE:TypeError: ord() expected a character, but string of length 3 found (Was: Updated python-uncertainties)

Hello Andreas, > Patches are welcome (I have no idea what the construct is doing neither > how to replace it with something valid). > Patch welcome as well - preferably as commit to Git. done but now, we need to understand why lintian complain about python module at the wrong place before uploa

RE:TypeError: ord() expected a character, but string of length 3 found (Was: Updated python-uncertainties)

Hello, here a diff between the python3.6 and python3.7 modules once updated via 2to3. r:/tmp$ diff core* 174c174 < for (variance, tag) in zip(variances, tags)) --- > for (variance, tag) in list(zip(variances, tags))) 181c181 < for (coords, value) in zip(trans

  1   2   >