Hello Piotr,
I am struggling, with the build system.
I will speak about this solution
> | override_dh_auto_build:
> | dh_auto_build -- --after-build '{interpreter} setup.py build_man'
the code instrumented of the BuildMan is this one
class BuildMan(Command):
"""Command to build man p
> 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
> 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
> 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
> 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
> 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
> 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
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 -- -
> 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
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
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
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
> 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
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
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_
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
> 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
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
> 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
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
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
Hello, just for information what is the difference with
pypi-install from the pyton-stdeb package
> 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
> 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
> 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
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
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
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
> > 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
> 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',
>
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
> 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
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
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
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.
101 - 135 of 135 matches
Mail list logo
