cifsy kaxictulm vhcez. vzabroi giuhvmh
Some brokers claim
to get you the. r a
t e. less than 4.0 % but they
eejfpih trrbxqs hufmxo lrqedcqxe
never do. We can really provide
you with 2.0 .f
i xed .ra
t e with 0
Tytexa cetlq htqoqd. zirsphth
down payment for all states
except Alabama.
rllsax
Heyho!
Is somebody working on #488258 (python-lxml doesn't include documentation)?
Matthias: would you accept and upload a patch if I would prepare one?
I've been browsing the included text files, but it's a bit a pain, and there
are references to the auto-built api docs which
Hello,
My package generates its documentation with sphinx. I'm wondering what
license the resulting generated files fall under. In particular:
1. I guess that the generated HTML files have the same license as the .rst
files they're generated from, right?
2. The included sphinx te
o find a debian package providing these tools.
Should I :
* look better (any hint welcome)
* file a bug report against the python packages, requesting a
python-doc-tools package to be added to the debian archive
* ship my own version of mkhowto in the package to build the
documentation
Any sug
* Nikolaus Rath , 2011-07-09, 15:03:
3. What is the license of autogenerated javascript libraries like
_static/underscore.js
Err, this one is by no means autogenerated.
https://bitbucket.org/birkenfeld/sphinx/changeset/b7fb19a0992d
--
Jakub Wilk
--
To UNSUBSCRIBE, email to debian-python-requ
Jakub Wilk writes:
> * Nikolaus Rath , 2011-07-09, 15:03:
>>3. What is the license of autogenerated javascript libraries like
>>_static/underscore.js
>
> Err, this one is by no means autogenerated.
> https://bitbucket.org/birkenfeld/sphinx/changeset/b7fb19a0992d
Oh, I see. It looked pretty autoge
n pythonX.Y-doc.
Note that you need some other files for mkhowto to work, a texinput
file and some additional scripts, one perl script...
your build-depends should get quite big :)
> * ship my own version of mkhowto in the package to build the
> documentation
You can do that too, until the scr
o be added to the debian archive
> I'suggest not a new package, but inclusion in pythonX.Y-doc.
Why would we need the python documentation to build our own
documentation? I think a new package is a better idea.
> Note that you need some other files for mkhowto to work, a texinput
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, May 09, 2003 at 04:03:28PM +0200, Martin SjÃgren wrote:
> Why would we need the python documentation to build our own
> documentation?
What do you mean with "our own"?
> Tell me about it! Look at the build-dependencie
ckage, but inclusion in pythonX.Y-doc.
Uhm, no. Only documentation in /usr/share/doc/ belongs
into -doc packages (documented in policy). But these tools are code
and should be shipped separately. So I would vote for the original
python-doc-tools suggestion.
Kind regards
Andreas.
e distribution) be available.
>
> I've been unable to find a debian package providing these tools.
>
> Should I :
>
> * file a bug report against the python packages, requesting a
> python-doc-tools package to be added to the debian archive
> * ship my own version of
Hello,
is there any recipe/snippet for how to install or treat a sphinx based
python package documentation in debian/rules?
Thanks in advance,
Timmie
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Conta
there are manpages: pybuild¹, dh_python3² / dh_python2³ / dh_pypy⁴
there's a wiki page⁵ with examples, there's even
/usr/share/doc/dh-python/README.PyDist⁶ and a talk⁷ about pybuild during
DebConf... but people still tell me dh-python's documentation sucks
so...
How can I improve
Howdy all,
Where is the best location for library documentation of a Debian Python
library package?
Debian Policy §12.3 says:
[…] installing the documentation into the documentation directory of
the main package is preferred since it is independent of the
packaging method and will
Hello world,
python-sphinx 1.0.7-4, which I uploaded yesterday, fixes incompatibility
between its own javascript code and recent versions of jQuery that made
the search function pretty unusable (bug #625208).
The bad news is that almost all packages shipping Sphinx-generated
documentation
On Wed, May 23, 2012 at 11:02:30PM +0200, Tim Michelsen wrote:
> Hello,
> is there any recipe/snippet for how to install or treat a sphinx
> based python package documentation in debian/rules?
Hi,
Have you looked at dh_sphinxdoc?
regards,
iustin
--
To UNSUBSCRIBE, email to debian-py
lintian4python (>= 0.5) is now able to detect some common problems with
Sphinx-generated documentation, which break the search functionality.
Please consider fixing your packages! :) Please test your packages
before uploading, as there might be other, undetected problems with
them. If you
Hi Piotr,
On Mon, 26 Oct 2015, Piotr Ożarowski wrote:
> How can I improve it? Do you need more detailed description of options?
> Do you need more examples? Or maybe I should hide most of options, the
> "corner case" ones? I focus on making things work out of the box, if
> possible, and make it ve
On Oct 26, 2015, at 06:28 PM, Raphael Hertzog wrote:
>I for one lack a high level presentation of how the various bits work together
>and a clear description of the "magic" behind each tool.
I agree with this. When you know where to look, the documentation is actually
quite go
On 26.10.2015 12:36, Piotr Ożarowski wrote:
there are manpages: pybuild¹, dh_python3² / dh_python2³ / dh_pypy⁴
there's a wiki page⁵ with examples, there's even
/usr/share/doc/dh-python/README.PyDist⁶ and a talk⁷ about pybuild during
DebConf... but people still tell me dh-python'
> > Can you be more specific about what's missing?
>
> I for one lack a high level presentation of how the various bits work together
here's what I got so far (I wanted to provide it as
/usr/share/doc/dh-python/README). I stopped working on it because now I
have to prove dh-python is not responsi
On Oct 28 2015, Piotr Ożarowski wrote:
>> > Can you be more specific about what's missing?
>>
>> I for one lack a high level presentation of how the various bits work
>> together
>
> here's what I got so far (I wanted to provide it as
> /usr/share/doc/dh-python/README).
Looks great. That would
> > I stopped working on it because now I
> > have to prove dh-python is not responsible for maintainers that override
> > dh_auto_install and rm egg-info or new "features" in python3.5
>
> I don't understand that sentence.
it's just my rant of the day. Each day I choose a victim and enable
Piotr
On Oct 28, 2015, at 05:59 PM, Piotr Ożarowski wrote:
>Each day I choose a victim and enable Piotr's evil mode.
Beware the Eye of Piotr.
:)
-Barry
Matthias Klose writes:
> I'd like to see a section with examples too, maybe even referencing
> particular
> packages, which show good practice for a given use case, or which demonstrate
> some feature.
Examples of how to override dh_auto_test to run custom tests would be
good. It seems to be
ould be overriding it?
Thanks.
Christopher
On 16 July 2017 at 05:54, Ben Finney wrote:
> Howdy all,
>
> Where is the best location for library documentation of a Debian Python
> library package?
>
> Debian Policy §12.3 says:
>
> […] installing the documentation int
Look at Debian Policy, section 12.3 Additional Documentation. The answer is
there.
Scott K
On Saturday, March 03, 2018 09:25:20 AM Christopher Hoskin wrote:
> Dear Ben,
>
> Did you get an answer to this?
>
> I've just noticed a change in behavior of dh_installdocs betwee
Thanks - so the policy is that the preference is that documentation is
installed in /usr/share/doc/, but that
/usr/share/doc/-doc is also allowed. The justification
is that the documentation is easier for users to find this way.
dh_installdocs attempts to compute the name of main package by
(Sorry if this has been discussed before: it's not obvious how to search
for it)
Policy 12.3 [0] states that documentation for $package should preferably
be packaged as $package-doc but still install to /usr/share/doc/$package
not /usr/share/doc/$package-doc. By default, debhelper imple
Hello. While removing a py2 subpackage I noticed the following difference:
- in the old version -doc ships /usr/share/doc/python-foo/
- in the new version -doc ships /usr/share/doc/python-foo-doc/
During the new version build process, dh_installdocs complains about
main package auto-detection. You
Le Fri, 20 May 2011 22:09:22 +0200,
Jakub Wilk a écrit :
> Hello world,
>
> python-sphinx 1.0.7-4, which I uploaded yesterday, fixes incompatibility
> between its own javascript code and recent versions of jQuery that made
> the search function pretty unusable (bug #625208).
Should we add a B
* Picca Frédéric-Emmanuel ,
2011-05-24, 09:39:
python-sphinx 1.0.7-4, which I uploaded yesterday, fixes
incompatibility between its own javascript code and recent versions of
jQuery that made the search function pretty unusable (bug #625208).
Should we add a Build-Dep: python-sphinx (>= 1.0.7
My package distributes a pydoc directory, but setup.py does not rebuild it.
What is the usual way to rebuild this directory from scratch?
What is the proper way to publish the api info in this directory?
Is there a example package that does this stuff correctly?
Thank You for your response.
-
Hello,
I wish there was a python-requests-doc package for browsing
python-requests' documentation offline. I'd like to add it if I can.
I saw that debian/watch currently targets the PyPI tarball, which lacks
the documentation.
As a first step, I'm submitting a merge request [1]
Quoting "anatoly techtonik" :
That's not sufficient. To update Trac environment you will need to run
"trac-admin upgrade" and optionally "trac-admin wiki upgrade". The
second point is that web-servers (including Apache) treat symlinks
differently and I am unsure how to setup web permissions corre
Just figured it out so decided to share, may be it impacts your packages
as well...
I've detected that many of the packages of ours shipping
sphinx-generated html documentation cannot search offline -- just
produces stale "Searching ..."
The reason was — they were built with
Package: debian-policy
X-Debbugs-CC: debhelper-de...@lists.alioth.debian.org,
debian-python@lists.debian.org
Hi!
[ Promised follow up to the Python BoF at DebConf ]
For historical reasons, Python 2 modules are packaged as python-foo while
Python 3 modules are python3-foo. Documentation was
ckage for browsing
> python-requests' documentation offline. I'd like to add it if I can.
>
> I saw that debian/watch currently targets the PyPI tarball, which lacks
> the documentation.
Yes, I usually preferred PyPI distribution, but I'm fine switching since it
will enh
On Tue, 31 Dec 2019, 7:42 pm Daniele Tricoli, wrote:
> Hello Fabrice,
> thanks for pinging I did not notice the MR :(
> Please next time can you assign it to me? I should reveive some sort of
> notification I hope! :)
>
I recommend you enable notifications for all packages in you are interested
Hello Daniele,
Daniele Tricoli writes:
> Please next time can you assign it to me? I should reveive some sort of
> notification I hope! :)
Sure, will do.
I have updated the merge request.
For d/changelog, I used "debchange -i" which for some reason chose
"2.22.0-2.1", I've changed it to "2.22.
Hi Fabrice,
Fabrice BAUZAC-STEHLY writes:
> Hello Daniele,
>
> Daniele Tricoli writes:
>
>> Please next time can you assign it to me? I should reveive some sort of
>> notification I hope! :)
>
> Sure, will do.
>
> I have updated the merge request.
>
> For d/changelog, I used "debchange -i" which
Hello Fabrice,
On Thu, Jan 02, 2020 at 08:46:51AM +0100, Fabrice BAUZAC-STEHLY wrote:
> I have updated the merge request.
Merged, many thanks for your contribution!
Regards,
--
Daniele Tricoli 'eriol'
https://mornie.org
signature.asc
Description: PGP signature
Hello Mattia,
On Tue, Dec 31, 2019 at 09:15:12PM +0100, Mattia Rizzolo wrote:
> I recommend you enable notifications for all packages in you are interested
> in, by setting the notification switch on salsa to "watch".
Many thanks for the hint, I was not aware of this!
> Otherwise, you could get
Section : python
It builds those binary packages:
python-mockito-doc - Spying framework for Python - documentation
python3-mockito - Spying framework for Python
To access further information about this package, please visit the following
URL:
https://mentors.debian.net/pack
On Tue, Dec 29, 2009 at 6:10 PM, W. Martin Borgert wrote:
>
> There is an open bug report anyway, that suggests and
> "trac-admin upgrade" to be done automatically on every
> upgrade of Trac. This is technically too difficult to solve,
> because one never knows which environments exist (they
> mig
-foo-doc packages deliberately ignoring it seems wrong.
In dbus-python I left the documentation in /usr/share/doc/python-dbus-doc
(overriding dh_installdocs), but put symlinks to it in
/usr/share/doc/python{,3}-dbus so that users can find it by following
the Policy-recommended route. Maybe that's a
* License : BSD 3-Clause
Programming lang : Python
Upstream git : https://github.com/astropy/sphinx-automodapi
Pypi URL : https://pypi.python.org/pypi/sphinx-automodapi
Description : Sphinx extensions for generating API documentation
The sphinx-automodapi package
I'm trying to package pwclient, which depends on python3-pbr and has a
rudimentary manual page generated from Sphinx documentation. Is there
a similar example package which I can look at, to see how to trigger
the manual page generation?
I currently get this:
dh_sphinxdoc: warning: S
On 9/19/21 2:29 PM, Fabrice Bauzac-Stehly wrote:
> python-mockito (1.2.2-2) unstable; urgency=medium
> .
>* Source-only upload.
Hi, I do not see these changes in salsa. Still the old changelog.
can you push? I'll happily sponsor
Cheers,
--
Nilesh Patra
Debian Developer, Uploading
⢀⣴⠾
Nilesh Patra writes:
> On 9/19/21 2:29 PM, Fabrice Bauzac-Stehly wrote:
>> python-mockito (1.2.2-2) unstable; urgency=medium
> Hi, I do not see these changes in salsa. Still the old changelog.
> can you push? I'll happily sponsor
Oops, done. Thanks!
--
Fabrice Bauzac-Stehly
PGP 01EEACF8244
Package: wnpp
Severity: normal
X-Debbugs-Cc: pyca...@packages.debian.org, debian-python@lists.debian.org
Control: affects -1 + src:pycares
I intend to orphan the pycares package.
The package description is:
pycares is a Python 3 module which provides an interface to c-ares. c-ares is
a C librar
On Tuesday 27 October 2015 16:36:15 Brian May wrote:
> Sounds like we might have to repackage the source to drop the entire
> docs directory and remove the python-celery-doc package :-(
It might be helpful to bring upstream's attention to the matter...
--
Regards,
Dmitry Smirnov.
signature.as
On 2020-05-04 19:13:38 +0200 (+0200), Florian Weimer wrote:
> I'm trying to package pwclient, which depends on python3-pbr and has a
> rudimentary manual page generated from Sphinx documentation. Is there
> a similar example package which I can look at, to see how to trigger
>
On 2020-05-04 19:07:00 + (+), Jeremy Stanley wrote:
> On 2020-05-04 19:13:38 +0200 (+0200), Florian Weimer wrote:
> > I'm trying to package pwclient, which depends on python3-pbr and has a
> > rudimentary manual page generated from Sphinx documentation. Is there
&
Hi,
as per bug #1064979 python-cryptography was orphaned. Actually the
process of orphaninig is defined differently[1] by setting QA team as
maintainer. In this case DPT remains maintainer but there is no
Uploader specified any more. I personally will not add my ID as
Uploader. I have added th
Le jeu. 29 févr. 2024 à 12:06, Andreas Tille a écrit :
> Hi,
>
> as per bug #1064979 python-cryptography was orphaned. Actually the
> process of orphaninig is defined differently[1] by setting QA team as
> maintainer. In this case DPT remains maintainer but there is no
> Uploader specified any
building project
documentation
MkDocs is a fast, simple and downright gorgeous static site generator
that's geared towards building project documentation. Documentation
source files are written in Markdown, and configured with a single YAML
configuration file.
This package is required to buil
: BSD-2-clause
Programming Lang: Python
Description : Swagger Documentation Generator for Django REST Framework
This project is built on the Django REST Framework Docs and uses the Swagger
from Wordnik as an interface. This application introspectively generates
documentation based on your
: Python
Description : expand Python's enum module in Sphinx documentation
The enum_tools Sphinx extension can be used to document Enums better
than autoclass can currently. Additionally, this library includes a
decorator to add docstrings to Enum members from a comment at the end of
the
Hi Brian,
On Fri, 13 Feb 2015 10:06:25 +1100, Brian May wrote:
> MkDocs is a fast, simple and downright gorgeous static site generator
> that's geared towards building project documentation. Documentation
> source files are written in Markdown, and configured with a single YAML
&
On 13 February 2015 at 22:03, Dmitry Shachnev wrote:
> Thank you, I also need this package because Python-Markdown is going to
> use it for building its docs as well at some point in the future (will
> need to think how to avoid the circular dependency though).
>
Circular build depends, what fun
On 14 February 2015 at 09:52, Brian May wrote:
> What should I call the package? mkdocs? Or python3-mkdocs?
>
Thinking about this, I will call the source python-mkdocs, but the binary
package just mkdocs.
As I think the names python-mkdocs and python3-mkdocs imply some sort of
public and stable
://github.com/sphinx-contrib/emojicodes
* License : BSD-3-clause
Programming Lang: Python
Description : Sphinx extension to use emoji codes in Sphinx documentation
This extension allows one to write things like |:smile:| in Sphinx
documentation.
This package is a (recursive
Dmitry Smirnov writes:
> "docs/copyright.rst" clearly states that the documentation is licensed as
> non-DFSG CC-BY-NC-SA-3.0:
Also ./LICENSE contains:
Documentation License
=====
The documentation portion of Celery (the rendered contents of the
"
Am Thu, Feb 29, 2024 at 02:06:25PM -0800 schrieb Vagrant Cascadian:
> On 2024-02-29, Sandro Tosi wrote:
> > I intend to orphan the mpl-sphinx-theme package.
> >
> > The package description is:
> > This is the official Sphinx theme for Matplotlib documentation. It
com/manrajgrover/py-spinners>
* License : Expat
Programming Lang: Python
Description : rich and extensible flavor of Markdown meant for
technical documentation
and publishing
.
MyST is a flavor of markdown that is designed for simplicity, flexibility,
and extensibility. It conta
Dear Friends,
I was just looking for documentation about what's keeping us from
getting to python 3 but couldn't find anything which I could lay my
finger on.
I did find some obsolete documentation though on the wiki. The entries
can be seen at -
https://wiki.debian.org/Python
ces to
help it happen.
In the meantime, there is already documentation for people who wish to
become Debian package maintainers.
> Ok. I may be wrong. Do you have a list of literature for people who
> want to become a maintainer of Python package?
Start with the documentation for those wh
On Wed, Jun 06, 2018 at 08:38:56PM +0530, shirish शिरीष wrote:
> I was just looking for documentation about what's keeping us from
> getting to python 3
Depends on your definition of "getting to python 3".
> I have also been trying to understand which packages/modules are
at bottom :-
On 06/06/2018, shirish शिरीष wrote:
> Dear Friends,
>
> I was just looking for documentation about what's keeping us from
> getting to python 3 but couldn't find anything which I could lay my
> finger on.
>
> I did find some obsolete documentation
On Wed, Jun 06, 2018 at 10:20:13PM +0530, shirish शिरीष wrote:
> Maybe it would have been better to say that right now python gives
>
> $ python --version
> Python 2.7.15
>
> To be more precise, I meant to know if 'Bullseye' i.e Debian 11 would
> have python 3.0 as default or not.
/usr/bin/pytho
shirish शिरीष writes:
> On 06/06/2018, shirish शिरीष wrote:
> > I have also been trying to understand which packages/modules are
> > remaining for python 3 to be the default-python
There is no “default Python” in Debian. Python 2 and Python 3 are
separate run-time systems, and are provided by d
Hi,
2018-06-07 11:03 GMT+02:00 Ben Finney :
>
> There is no “default Python” in Debian
> ...
> There is no command in Debian for “the default Python”,
> ...
> There is no “default Python” in Debian.
>
do I understand you correctly that there is no default Python in Debian? :)
Just kiddin', t
Ondrej Novy writes:
> do I understand you correctly that there is no default Python in
> Debian? :)
:-) Hopefully a little polite repetition will help the point become
clearer, though Andrey said it plainly in the initial response.
Shirish, now that we've established there is no “default Python
74 matches
Mail list logo
