Hi Timo,
Timo Röhling writes:
> * Ole Streicher [2024-11-18 13:40]:
>>Build log is f.e.
>>https://salsa.debian.org/debian-astro-team/pybdsf/-/jobs/6612895
> The problem is most likely caused by "find_package(F2PY)", which does
> not take different Python vers
Hi,
I have a package (pybdsf) that currently fails to compile when both
Python 3.12 and 3.13 are installed (current situation). From the log:
8<-
I: pybuild plugin_pyproject:129: Building wheel for python3.13 with "build"
module
I: pybuild base:311: py
Package: wnpp
Severity: wishlist
Owner: Ole Streicher
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-python@lists.debian.org,
debian-as...@lists.debian.org
* Package name: asdf-unit-schemas
Version : 0.1.0
Upstream Author : The ASDF Developers
* URL : https
Package: wnpp
Severity: wishlist
Owner: Ole Streicher
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-python@lists.debian.org,
debian-as...@lists.debian.org, debian-scie...@lists.debian.org
* Package name: ewah-bool-utils
Version : 1.0.2
Upstream Author : Matthew Turk
Scott Kitterman writes:
> On December 4, 2022 3:42:15 PM UTC, Ole Streicher wrote:
>>So I would suspect that it is already the build does something wrong
>>here. Which package is that? pybuild-plugin-pyproject?
>
>
> python3-installer
Thank you, I filed a bug.
Best
Ole
Hi Scott,
thanks for the hint.
Scott Kitterman writes:
> My first guess is that in some circumstances setuptools is doing the
> installing
> and in others it's the dh-python pyproject plugin (using the installer
> module). Looking at the build log on buildd.d.o, I can see that build is
> us
Hi,
I need some help with a package that switched to using pyproject.toml
only. The package is asdf-astropy, and the problem I have that it does
not package all Python files recursively: for example astropy_asdf.io
files are missing (as seen in unstable now).
https://tracker.debian.org/pkg/asdf-a
Scott Talbert writes:
> On Fri, 12 Aug 2022, Ole Streicher wrote:
>> Scott Talbert writes:
>>> On Thu, 11 Aug 2022, Ole Streicher wrote:
>>>> E: pybuild pybuild:369: build: plugin pyproject failed with: UNKNOWN
>>>> wheel found: UNKNOWN-1.0.3-py3-none-a
Scott Talbert writes:
> On Thu, 11 Aug 2022, Ole Streicher wrote:
>> ---8<---
>> * Building wheel...
>> Successfully built UNKNOWN-1.0.3-py3-none-any.whl
>> I: pybuild plugin_pyproject:118: Unpacking whee
Hi,
I have a package
https://salsa.debian.org/debian-astro-team/asdf-standard
that changed its build process to pyproject.toml. As hinted by pybuild,
I added pybuild-plugin-pyproject to the build dependencies; however it
still does not build properly. The build fails with the following
output:
Package: wnpp
Severity: wishlist
Owner: Ole Streicher
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-as...@lists.debian.org,
debian-python@lists.debian.org
Control: block 1012441 by -1
* Package name: specreduce-data
Version : 0+git2021.11.18
Upstream Author : Astropy
Package: wnpp
Severity: wishlist
Owner: Ole Streicher
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-as...@lists.debian.org,
debian-python@lists.debian.org
Control: block 1012441 by -1
* Package name: synphot
Version : 1.1.2
Upstream Author : Space Telescope Science
Package: wnpp
Severity: wishlist
Owner: Ole Streicher
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-as...@lists.debian.org,
debian-python@lists.debian.org
* Package name: specreduce
Version : 1.0.0
Upstream Author : Astropy Specreduce contributors
* URL
Package: wnpp
Severity: wishlist
Owner: Ole Streicher
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-python@lists.debian.org,
debian-as...@lists.debian.org
* Package name: asdf-standard
Version : 1.6.0
Upstream Author : The ASDF Developers
* URL : https
Package: wnpp
Severity: wishlist
Owner: Ole Streicher
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-python@lists.debian.org,
debian-as...@lists.debian.org, debian-scie...@lists.debian.org
* Package name: cmyt
Version : 1.0.4
Upstream Author : Clement Robert
* URL
Package: wnpp
Severity: wishlist
Owner: Ole Streicher
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-python@lists.debian.org,
debian-as...@lists.debian.org
* Package name: asdf-wcs-schemas
Version : 0.1.1
Upstream Author : The ASDF Developers
* URL : https
Package: wnpp
Severity: wishlist
Owner: Ole Streicher
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-python@lists.debian.org,
debian-as...@lists.debian.org
* Package name: asdf-coordinates-schemas
Version : 0.1.0
Upstream Author : The ASDF Developers
* URL
Package: wnpp
Severity: wishlist
Owner: Ole Streicher
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-python@lists.debian.org,
debian-as...@lists.debian.org
* Package name: asdf-transform-schemas
Version : 0.2.0
Upstream Author : The ASDF Developers
* URL
Package: wnpp
Severity: wishlist
Owner: Ole Streicher
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-python@lists.debian.org,
debian-as...@lists.debian.org
* Package name: asdf-astropy
Version : 0.1.2
Upstream Author : The ASDF Developers
* URL : https
Package: wnpp
Severity: wishlist
Owner: Ole Streicher
X-Debbugs-Cc: debian-de...@lists.debian.org,
debian-python@lists.debian.org, debian-as...@lists.debian.org
* Package name: mpl-animators
Version : 1.0.0
Upstream Author : Sunpy Developers
* URL : https
Hi Nilesh, Andrey,
Nilesh Patra writes:
> On 10/30/21 5:50 PM, Ole Streicher wrote:
>> Hi,
>> https://salsa.debian.org/debian-astro-team/pyraf/-/jobs/2130878#L2062
>> How can one find out the correct machine here?
>
> I just committed something to salsa -- sort of a
Hi,
I have a package (pyraf) where I need to switch off some tests for i386
(but not for other 32-bit platforms). I do this by
import platform
is_i386 = platform.machine() in ('i386', 'i486', 'i586', 'i686')
[...]
@pytest.mark.skipif(is_i386, reason='diff is not identical on i386')
def test_gki
Package: wnpp
Severity: wishlist
Owner: Ole Streicher
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-python@lists.debian.org,
debian-as...@lists.debian.org
* Package name: casa-formats-io
Version : 0.1
Upstream Author : Thomas Robitaille
* URL : http://casa
Package: wnpp
Severity: wishlist
Owner: Ole Streicher
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-python@lists.debian.org,
debian-as...@lists.debian.org, debian-scie...@lists.debian.org
* Package name: unyt
Version : 2.8.0
Upstream Author : Nathan Goldbaum
* URL
Paul Wise writes:
> On Thu, Jan 21, 2021 at 3:42 PM Ole Streicher wrote:
>
>> But this is also the case for all packages which implicitly depend on
>> other packages which are not available on some architectures.
>
> This is true, but it doesn't make for a good user
Paul Wise writes:
> On Thu, Jan 21, 2021 at 1:12 PM Ole Streicher wrote:
>
>> This would be a quite flexible and extendible approach to have packages
>> installable only where they work.
>
> There is precedent for this sort of thing in the isa-support source
> packag
Ansgar writes:
> On Thu, 2021-01-21 at 13:46 +0100, Ole Streicher wrote:
>> I am still wondering why we don't have just empty some pseudo-
> packages that are available only on specific architectures
>> (or groups of them, like linux, or little endian, or 64 bit or
Paul Wise writes:
> This is what I eventually chose for iotop. At the time I wanted dpkg
> and dak to support something like Architecture: linux-all, which would
> build arch: all packages, but only put them in the Packages files for
> the Linux architectures.
>
> I am now thinking that a more gen
Package: wnpp
Severity: wishlist
Owner: Ole Streicher
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-as...@lists.debian.org,
debian-python@lists.debian.org
* Package name : astroalign
Version : 2.3.1
Upstream Author : Martin Beroiz
* URL : http
Package: wnpp
Severity: wishlist
Owner: Ole Streicher
X-Debbugs-Cc: debian-python@lists.debian.org, debian-de...@lists.debian.org
* Package name : tifffile
Version : TBD
Upstream Author : Christoph Gohlke <mailto:cgoh...@uci.edu>
* URL : https://pypi.org/project/tifffile/#descr
Package: wnpp
Severity: wishlist
Owner: Ole Streicher
X-Debbugs-Cc: debian-python@lists.debian.org, debian-de...@lists.debian.org,
debian-as...@lists.debian.org
* Package name: pyerfa
Version : TBD
Upstream Author : Astropy Developers
* URL : https://github.com
Package: wnpp
Severity: wishlist
Owner: Ole Streicher
X-Debbugs-Cc: debian-python@lists.debian.org, debian-de...@lists.debian.org,
debian-as...@lists.debian.org
* Package name: pybdfs
Version : 1.9.2-1
Upstream Author : LOFAR/Astron
* URL : https://www.astron.nl/citt
Package: wnpp
Severity: wishlist
Owner: Ole Streicher
X-Debbugs-Cc: debian-python@lists.debian.org,
debian-de...@lists.debian.org
* Package name: extension-helpers
Version : 0.1
Upstream Author : The Astropy Developers
* URL : https://pypi.org/project/extension
Hi,
we have a source package (older packaging attempt in gavodachs [1],
Arch:all) that builds a number of binary packages. Specifically:
python3-gavo-stc gavo/stc/
python3-gavo-utils gavo/utils/, gavo/imp
python3-gavo-votable gavo/votable
python3-gavo all other gavo/* + 2 entry poin
Package: wnpp
Severity: wishlist
Owner: Ole Streicher
X-Debbugs-Cc: debian-python@lists.debian.org, debian-de...@lists.debian.org,
debian-as...@lists.debian.org
* Package name: pytest-filter-subpackage
Version : 0.1.1
Upstream Author : Thomas Robitaille
* URL : https
Hi Dmitry,
Dmitry Shachnev writes:
> On Thu, Dec 19, 2019 at 01:09:40PM +0100, Ole Streicher wrote:
>> 2. dh_auto_test then tries runs the tests in .pybuild. If the test need
>> data files installed, they must be copied manually (right?).
>
> You can use debian/pybuild.testf
Hi,
I am currently updating scikit-image (skimage) to its newest version,
and I have some difficulties to understand how pybuild works (for
setup.py packages):
1. first, dh_auto_build calls "python3.X setup.py build" to create the
packages (Python files and compiled extensions) in
..pybuild/cpyth
Hi,
I am currently updating the "casacore" package to the latest upstream
version. Doing this, I discovered that it is not marked as part of the
Python 3.8 transition, and was also not binNMUed for this, although it
has the package libcasa-python3-3 (to be renamed to libcasa-python3-4)
that depend
Package: wnpp
Severity: wishlist
Owner: Ole Streicher
X-Debbugs-Cc: debian-python@lists.debian.org, debian-de...@lists.debian.org,
debian-as...@lists.debian.org
* Package name: pytest-astropy-header
Version : 0.1.1
Upstream Author : Thomas Robitaille
* URL : https
Félix Sipma writes:
> They just run "python3 setup.py install"
> (https://github.com/scheibler/khard/issues/231):
> [...]
>
> For my part, I "just" build the debian package with "gbp buildpackage",
> and with "dh $@ --with python3 --buildsystem=pybuild" in debian/rules.
>
> The solutions I say ar
Hi IOhannes,
I have basically the same problem, funnily with almost the same subject:
https://lists.debian.org/debian-python/2019/09/msg00040.html
The difference is, that the "external" subdirectory is not copied. So,
it seems to be a bug in dh-python.
Cheers
Ole
"IOhannes m zmölnig (Debian/G
Hi,
I am not sure whether this is a bug in dh-python or if something is
wrong with my package (python-asdf). The package has an (almost)
standard setup, so dh_build is not overridden.
However, when I try to package, some subdirectories are not copied;
namely `asdf/external`:
Hi,
I have a package (sunpy) that in the latest registers an entry point for
another package (asdf):
[options.entry_points]
asdf_extensions =
sunpy = sunpy.io.special.asdf.extension:SunpyExtension
This functionality is also used during some tests, which I would like to
keep.
However, pybuild
Package: wnpp
Severity: wishlist
Owner: Ole Streicher
X-Debbugs-Cc: debian-as...@lists.debian.org, debian-de...@lists.debian.org,
debian-python@lists.debian.org
* Package name : parfive
Version : 1.0.0
Upstream Author : Stuart Mumford
* URL : https://github.com
Mattia Rizzolo writes:
> On Mon, Jan 07, 2019 at 09:03:11AM +0100, Ole Streicher wrote:
>> The problem is that aplpy uses matplotlib, and the old matplotlib uses
>> the deprecated numpy function np.asscalar(), which leads to a
>> DeprecationWarning, which is (on purpose, b
Mattia Rizzolo writes:
> On Sun, Jan 06, 2019 at 05:07:41PM +0100, Ole Streicher wrote:
>> Now it turns out that there is a new migration problem, which is aplpy:
>> Current aplpy (2.0~rc2-2) CI test works well
>
> You probably mean aplpy 1.1.1-4.
No, I meant the one above (
Mattia Rizzolo writes:
> On Sat, Jan 05, 2019 at 08:30:28PM +0100, Ole Streicher wrote:
>> This would remove one dependent party (release team) from the chain of
>> blocking causes for the migration.
>
> Given your email on -mentors a few minutes ago I see there are troubles
Mattia Rizzolo writes:
> On Sat, Jan 05, 2019 at 04:02:35PM +0100, Ole Streicher wrote:
>> I'll do tonight. It however looks a bit suboptimal: when the CI test
>> with a new version fails for an old reverse dependency, then the new
>> version obviously breaks that old
Mattia Rizzolo writes:
> The way forward in cases like these is for the package that originally
> cuased the breakage (i.e. numpy) to declare a versioned Breaks on the
> borken and now fixed package (i.e. astropy (<< 3.1-1)). This way
> britney and debci will know they have to test numpy and astro
Mattia Rizzolo writes:
> The way forward in cases like these is for the package that originally
> cuased the breakage (i.e. numpy) to declare a versioned Breaks on the
> borken and now fixed package (i.e. astropy (<< 3.1-1)). This way
> britney and debci will know they have to test numpy and astr
Hi all,
Since a few days, a new RC is stalled in unstable:
testing: 1:1.15.4-2
unstable: 1:1.16.0~rc1-3
The reason that it can't migrate is that it breaks the CI tests of
several packages in testing. For example astropy (where I am the
uploader), and its dependencies. The CI test failures were
Package: wnpp
Severity: wishlist
Owner: Ole Streicher
X-Debbugs-Cc: debian-python@lists.debian.org, debian-de...@lists.debian.org
* Package name : sphinx-automodapi
Version : 0.9
Upstream Author : Thomas Robitaillie
* URL : https://astropy.org/sphinx-automodapi
On 27.11.18 09:35, Ondrej Novy wrote:
> út 27. 11. 2018 v 8:46 odesílatel Ole Streicher <mailto:oleb...@debian.org>> napsal:
>
> Thanks, however it turns out that this will unfortunately not work for
> me: from astropys POV, pytest seems to be broken in versions
Hi Ondrej,
On 26.11.18 21:29, Ondrej Novy wrote:
> my plan is:
>
> * keep 3.x for Buster
> * upgrade to >= 4.x just after Buster release
>
> Because we are going to drop Python after Buster release, I think it's
> perfectly fine that Astropy (Py2 version) will not support Pytest 4.x.
Thanks
Hi all,
since the EOL of Python 2 is approaching, the (python-) "astropy"
upstream has split its development into a Python 2.7 legacy branch
(2.0.X) and the normal development (3.X), where the legacy branch does
get only maintenance now. Since many Python 2 packages still depend on
astropy, I spli
Hi,
when I use dh_python3-ply in d/rules like this:
--8<---
override_dh_python3:
dh_python3-ply $$(find $(PYBUILD_DESTDIR_python3) -name '*tab.py')
dh_python3
--8<--
ghisv...@gmail.com writes:
> Indeed. Note that NumPy has already published plans to become Python 3
> only in the near future, so the deprecation of Python 2 in the
> scientific stack will happen eventually.
>
> I just don't think it should be rushed into the Buster release cycle.
If we really wan
Piotr Ożarowski writes:
>> >From the pybuild wiki page, I learned to do instead the override:
>>
>> export PYBUILD_TEST_ARGS=-k "not figure and not online"
>>
>> However, then the tests are not found anymore and the test step fails:
>
> 1) remove HOME line from debian/rules, pybuild sets one
> 2
Hi,
I already posted this two weeks ago, but didn't get a response yet, and
thus it remains unsolved:
For one of my packages (sunpy), I want to complete the switch to pybuild
by removing the custom (and quite unperfect) dh_override_auto_test rule.
Currently, I have the following lines in d/rules
Dmitry Shachnev writes:
> Sphinx 2.0 will also drop Python 2.7 support, so I am going to make the
> “sphinx” source package ship only python3-sphinx, and introduce the new
> source package (“sphinx-python2”?) which will ship only python-sphinx.
>
> Eventually I will also do a mass bug filing, but
Hi Andreas and Pythonies,
Andreas pointed me to the case that we have two repositories
"python-drizzle" which is confusing:
https://salsa.debian.org/python-team/modules/python-drizzle/
https://salsa.debian.org/debian-astro-team/python-drizzle
The reason for this is that in 2016, I took the "free
Hi,
For one of my packages (sunpy), I want to complete the switch to pybuild
by removing the custom (and quite unperfect) dh_override_auto_test rule.
Currently, I have the following lines in d/rules:
override_dh_auto_test:
python -m pytest sunpy -k "not figure and not online"
pyt
Hi,
I have (still) problems with PLY generated files in the astropy package:
they are just not generated, and I have no idea how to generate them
correctly. For example, there are the files
astropy/coordinates/angle_lextab.py
astropy/coordinates/angle_parsetab.py
which are now cleaned up in d/cl
Hi,
I am currently rewriting part of the blends-dev package which is used
for maintaining Debian Pure Blends into Python. This however comes out
some abstractions of Blends (namely the tasks infrastructure) that may
be re-usable on other places, f.e. in the blends.d.o web service. So it
is probabl
Hi,
I need some access (as normal user) to an apt cache with an alternative
sources.list (those in /etc/blends/ installed by blends-dev), but I have
problems to find out how to use it.
I first tried to just specify the alternative source file:
```
>>> import apt
>>> c = apt.Cache()
>>> c.update(
Dear Piotr,
Piotr Ożarowski writes:
> or even better (without using pybuild's internal paths):
>
> override_dh_auto_test:
> dh_auto_test -- --system=custom --test-args '{interpreter}
> {dir}/debian/tests/pyraf-test.py'
That is optimal for me. Thank you very much for the hint!
Best rega
Hi,
one of my Python packages has a test script under debian/tests that I
want to run at build time. The problem is now how to get the name of the
actual build directory, which is needed to be put into the PYTHONPATH:
Up to now, I did the following in debian/rules:
test-python%:
HOME=/tm
Thomas Goirand writes:
> On 03/13/2018 12:29 AM, Ghislain Vaillant wrote:
>> Imo, we should just make it clear in policy that source packages
>> should be named `foo` or `python-foo`,
>> and corresponding doc packages should be named `foo-doc` or `python-foo-doc`.
>
> Very often, "foo" is already
Piotr Ożarowski writes:
> [W. Martin Borgert, 2018-02-07]
>> And how about merging the modules and apps teams into one?
>
> I don't understand this, though. Why you want to merge them?
> Sure, packaging Python applications is very similar to packaging
> libraries but the difference is very signifi
Package: wnpp
Severity: wishlist
Owner: Ole Streicher
X-Debbugs-Cc: debian-python@lists.debian.org, debian-de...@lists.debian.org
* Package name: pytest-astropy
Version : 0.2.1
Upstream Author : Thomas Robitaille
* URL : https://github.com/astropy/pytest-astropy
Package: wnpp
Severity: wishlist
Owner: Ole Streicher
X-Debbugs-Cc: debian-python@lists.debian.org, debian-de...@lists.debian.org
* Package name: pytest-arraydiff
Version : 0.1
Upstream Author : Thomas Robitaille
* URL : https://github.com/astrofrog/pytest-arraydiff
Package: wnpp
Severity: wishlist
Owner: Ole Streicher
X-Debbugs-Cc: debian-python@lists.debian.org, debian-de...@lists.debian.org
* Package name: pytest-openfiles
Version : 0.2.0
Upstream Author : Thomas Robitaille
* URL : https://github.com/astropy/pytest-openfiles
Package: wnpp
Severity: wishlist
Owner: Ole Streicher
X-Debbugs-Cc: debian-python@lists.debian.org, debian-de...@lists.debian.org
* Package name: pytest-doctestplus
Version : 0.1.2
Upstream Author : Thomas Robitaille
* URL : https://github.com/astropy/pytest
Package: wnpp
Severity: wishlist
Owner: Ole Streicher
X-Debbugs-Cc: debian-python@lists.debian.org, debian-de...@lists.debian.org
* Package name: pytest-remotedata
Version : 0.1
Upstream Author : Thomas Robitaille
* URL : https://github.com/astropy/pytest-remotedata
Hi,
I am the maintainer of the "python-astropy" package, that currently
creates packages for both Python 2 and Python 3. Both packages have a
number of reverse dependencies.
Recently, upstream announced a new version 3.0 of astropy, which
supports Python 3 only, and I think of the best mid-term s
Hi,
I want to create a package (pyraf, #711038) for both Python2 and
Python3. While the package itself is still not Python 3 compatible,
upstream says that running through 2to3 will make it; however the
resulting code is not Python 2 compatible anymore.
Is there a way to instruct pybuild to run t
Package: wnpp
Severity: wishlist
Owner: Ole Streicher
X-Debbugs-Cc: debian-as...@lists.debian.org,debian-python@lists.debian.org
Control: block 711038 by -1
* Package name: stsci.tools
Version : 3.4.3
Upstream Author : Space Telescope Science Institute
* URL :
http
Package: wnpp
Severity: wishlist
Owner: Ole Streicher
X-Debbugs-Cc: debian-as...@lists.debian.org,debian-python@lists.debian.org
* Package name: radio-beam
Version : 0.1
Upstream Author : Eric Koch, Adam Ginsburg et al.
* URL : https://github.com/radio-astro-tools
Diane Trout writes:
>> What I am opposing is the suggestion to install, in the near to
>> medium
>> term, a command of exactly the same name that has subtly similar but
>> incompatible behaviour, when that behaviour *already* has a command –
>> ‘python3’ – that is widely used by those who need it.
ba...@debian.org writes:
> On Aug 3, 2017, at 23:23, Scott Kitterman wrote:
> You’re right that folks will still need Python 2 after 2020, and that
> their best option may be to build it themselves, but I don’t think
> they’ll be building and installing some old Debian package. Instead
> they may
Hi,
I have a large Java package (as a jar in /usr/share/java) that is
accompanied with some Jython intergration (Python file). Upstream provides
a small script that adds the jar to the classpath, and starts jython
with a local python.path.
How should I package this for Jython?
* where should th
Brian May writes:
> Should we be using PyPI as our source of packages? Or github?
I already had packages that use a helper to generate the version
information from the git repository, and therefore need the git metadata
to build from source. I could solve this with a "fake" helper that
uses debia
package: python-skimage
version: 0.12.3-2
severity: serious
The Python 2 version of skimage depends on a package "python-dask" that
is not available in Debian.
There is a patch that make the dependency optional; however the
dependency was not removed afterwards. For Python 3, this seems to work.
Package: wnpp
Owner: Ole Streicher
Severity: wishlist
X-Debbugs-Cc:
debian-de...@lists.debian.org,debian-as...@lists.debian.org,debian-python@lists.debian.org
* Package name: ginga
Version : 2.5.20160420043855-1
Upstream Author : Eric R. Jeschke
* URL : https
Package: wnpp
Owner: Ole Streicher
Severity: wishlist
X-Debbugs-Cc:
debian-de...@lists.debian.org,debian-as...@lists.debian.org,debian-python@lists.debian.org
* Package name: python-fitsio
Version : 0.9.8
Upstream Author : Eric Sheldon
* URL : https://github.com
Package: wnpp
Owner: Ole Streicher
Severity: wishlist
X-Debbugs-Cc:
debian-de...@lists.debian.org,debian-as...@lists.debian.org,debian-python@lists.debian.org
* Package name: asdf
Version : 1.0.1
Upstream Author : Erik Bray, Michael Droettboom
* URL : https
Package: wnpp
Owner: Ole Streicher
Severity: wishlist
X-Debbugs-Cc:
debian-de...@lists.debian.org,debian-as...@lists.debian.org,debian-python@lists.debian.org
* Package name: pysynphot
Version : 0.9.7
Upstream Author : Vicki Laidler et al.
* URL : http
Package: wnpp
Owner: Ole Streicher
Severity: wishlist
X-Debbugs-Cc:
debian-de...@lists.debian.org,debian-as...@lists.debian.org,debian-python@lists.debian.org
* Package name: emcee
Version : 2.1.0
Upstream Author : Dan Foreman-Mackey <https://github.com/dfm>
Scott Kitterman writes:
> On Wednesday, January 06, 2016 04:11:18 PM Ole Streicher wrote:
>> I already applied directly in alioth, but didn't get a response.
> According to Alioth, you're in the team already.
Oh, I see. I didn't check it again before I processed the
Hello all,
I would like to join the DPMT. I already have packages some Python
packages (python-astropy and many of its affiliated packages,
python-pywcs, python-astroml) under the hood of the Debian-Astro team.
In future I probably need to package dependencies like Bottleneck that
are not specific
Package: wnpp
Owner: Ole Streicher
Severity: wishlist
X-Debbugs-Cc:
debian-de...@lists.debian.org,debian-as...@lists.debian.org,debian-python@lists.debian.org
* Package name: pyephem
Version : 3.7.6.0
Upstream Author : Brandon Rhodes
* URL : http://rhodesmill.org
Package: wnpp
Owner: Ole Streicher
Severity: wishlist
X-Debbugs-Cc:
debian-de...@lists.debian.org,debian-as...@lists.debian.org,debian-python@lists.debian.org
* Package name: sunpy
Version : 0.6.1
Upstream Author : Sunpyy Developers
* URL : https://sunpy.org
Package: wnpp
Owner: Ole Streicher
Severity: wishlist
X-Debbugs-Cc:
debian-de...@lists.debian.org,debian-as...@lists.debian.org,debian-python@lists.debian.org
* Package name: montage-wrapper
Version : 0.9.8
Upstream Author : Thomas Robitaille
* URL : hhttp
Package: wnpp
Owner: Ole Streicher
Severity: wishlist
X-Debbugs-Cc:
debian-de...@lists.debian.org,debian-as...@lists.debian.org,debian-python@lists.debian.org
* Package name: specutils
Version : 0.1 (to be updated)
Upstream Author : Wolfgang Kerzendorf
* URL : https
Package: wnpp
Owner: Ole Streicher
Severity: wishlist
X-Debbugs-Cc:
debian-de...@lists.debian.org,debian-as...@lists.debian.org,debian-python@lists.debian.org
* Package name: photutils
Version : 0.1
Upstream Author : Larry Bradley and Brigitta Sipocz
* URL : https
Package: wnpp
Owner: Ole Streicher
Severity: wishlist
X-Debbugs-Cc:
debian-de...@lists.debian.org,debian-as...@lists.debian.org,debian-python@lists.debian.org
* Package name: astroml-addons
Version : 0.2.2
Upstream Author : Jake VanderPlas
* URL : http
Package: wnpp
Owner: Ole Streicher
Severity: wishlist
X-Debbugs-Cc:
debian-de...@lists.debian.org,debian-as...@lists.debian.org,debian-python@lists.debian.org
* Package name: astroscrappy
Version : 1.0.3
Upstream Author : Curtis McCully
* URL : https://github.com
Package: wnpp
Owner: Ole Streicher
Severity: wishlist
X-Debbugs-Cc:
debian-de...@lists.debian.org,debian-as...@lists.debian.org,debian-python@lists.debian.org
* Package name: reproject
Version : 0.2
Upstream Author : Thomas P. Robitaille, Steve Crawford
* URL : http
Package: wnpp
Owner: Ole Streicher
Severity: wishlist
X-Debbugs-Cc:
debian-de...@lists.debian.org,debian-as...@lists.debian.org,debian-python@lists.debian.org
* Package name: ccdproc
Version : 0.3.3
Upstream Author : Steve Crawford
* URL : http
Package: wnpp
Owner: Ole Streicher
Severity: wishlist
X-Debbugs-Cc:
debian-de...@lists.debian.org,debian-as...@lists.debian.org,debian-python@lists.debian.org
* Package name: spectral-cube
Version : 0.3
Upstream Author : Adam Ginsburg et al.
* URL : http://spectral
1 - 100 of 124 matches
Mail list logo
