was the 2→3 conversion
done in a non-backwards compatible fashion?
thanks
Stuart
--
Stuart Prescotthttp://www.nanonanonano.net/ stu...@nanonanonano.net
Debian Developer http://www.debian.org/ stu...@debian.org
GPG fingerprintBE65 FD1E F4EA 08F3 23D4 3C6D 9FE8 B8CD 71C5 D1A8
env instead. If
only API compatibility were more of a priority in python-land.
² I assume python-gtk2 is going to be a problem in itself some time soon.
--
Stuart Prescotthttp://www.nanonanonano.net/ stu...@nanonanonano.net
Debian Developer http://www.debian.org/ stu...@debian.
bian already has
too many administrative hurdles and piles of little rules that scare away
people. I'm yet to understand whether rules like this are created for
benefit of people who like to have a policy with which to berate others or
by people who like to impose order on the world around
checkout is in the devscripts
package for submitting patches to the bts.)
Making use of existing tools and extending them where necessary so that they
always work seems a lot more useful than creating some sort of flawed naming
scheme that will only ever sometimes work.
--
Stuart Prescotthttp
Thomas Goirand wrote:
> On 07/11/2013 09:07 PM, Stuart Prescott wrote:
>>
>>> Oh, I need this pyX package... Let's download it.
>>
>> You're using a python module name because you need to import it. If you
>> want to import modules, you want the
use case for pip, but it should hardly be
considered the pinnacle of python's achievements.
But I think I'll leave the rest of that rant (and the bit about what you
shoudl do in a virtualenv when you need both modules A and B but module A
needs C version 1.0 and module B n
harder for QA, it's harder for new maintainers and it's harder for casual
bug squashers. Without undertaking any sort of survey of packages, my
feeling is that the project is centralising on d/watch + uscan instead of
get-orig-source.
cheers
Stuart
--
Stuart Prescotthttp://
different ways of doing this in the archive; let's not let the
perpetual wait for the perfect to miraculously appear get in the way of
using the good that is right in front of us.
regards
Stuart
--
Stuart Prescotthttp://www.nanonanonano.net/ stu...@nanonanonano.net
Debian Deve
\
--binary $DEBS \
--source $DSC \
--log-file $CHANGES.adt.log \
--- adt-virt-schroot unstable-amd64-sbuild
cheers
Stuart
(this message was brought to you by the package testing fan club)
--
Stuart Prescotthttp://www.nanonanonano.net/ stu...@nanonanonano.net
Debian Developer http://w
this package in Debian.
cheers
Stuart
--
Stuart Prescotthttp://www.nanonanonano.net/ stu...@nanonanonano.net
Debian Developer http://www.debian.org/ stu...@debian.org
GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7
--
To UNSUBSCRIBE, email to debian-python
it to 1.3.0. If you're keen, you could
investigate that... but I perfectly understand waiting for upstream to release
their next version.
cheers
Stuart
--
Stuart Prescotthttp://www.nanonanonano.net/ stu...@nanonanonano.net
Debian Developer http://www.debian.org/ stu...@d
.conf:
[DEFAULT]
keyid = 0x1396F2F7
debian/gbp.conf (in the source package -- applies to everyone)
[DEFAULT]
pristine-tar = True
sign-tags = True
.git/gbp.conf (in my working copy -- applies only to me or could actually go
into ~/.gbp.conf):
[DEFAULT]
builder=sbuild
[git-buildpackage]
export-dir=..
to the git repo.
cheers
Stuart
--
Stuart Prescotthttp://www.nanonanonano.net/ stu...@nanonanonano.net
Debian Developer http://www.debian.org/ stu...@debian.org
GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7
--
To UNSUBSCRIBE, email to debian-p
log entry of "New
> upstream release."
Yes, and that should be fairly easy to implement too. (Interestingly, I
always passed --svn-noautodch to svn-bp as I found that particular feature
exceedingly annoying but that is of course at build time not at upgrade
time)
cheers
Stuart
--
Stuart
-migration.git
is there any reason to use a loop around git-import-dsc rather than git-
import-dscs --debsnap here?
thanks for reporting back from the BoF for us!
cheers
Stuart
--
Stuart Prescotthttp://www.nanonanonano.net/ stu...@nanonanonano.net
Debian Developer http://www.debian.org/
cause they are so crap in svn. In the past,
I didn't use these features either when I was only using svn. Now I know
they are useful things, I use them quite a lot because they are so easy and
efficient in git. When I go back to working on svn projects, I realise how
much the tool is deficient
titude will also then install packages of
lower priority to satisfy the dependencies.
--
Stuart Prescotthttp://www.nanonanonano.net/ stu...@nanonanonano.net
Debian Developer http://www.debian.org/ stu...@debian.org
GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7
practice to permit priority inversion for dependencies,
there's no reason to raise the priority of python3-apt.
--
Stuart Prescotthttp://www.nanonanonano.net/ stu...@nanonanonano.net
Debian Developer http://www.debian.org/ stu...@debian.org
GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7
to change the overrides are ready to be filed.
Additionally, changed dependencies are needed in:
* logrotate (Recommends: mailx → bsd-mailx | mailx), #849743
Your comments on (and hopefully assent to) these changes would be welcome.
cheers
Stuart
(Please CC me in replies)
--
Stuart Pr
now no
circular dependency?
(thinking aloud)
cheers
Stuart
--
Stuart Prescotthttp://www.nanonanonano.net/ stu...@nanonanonano.net
Debian Developer http://www.debian.org/ stu...@debian.org
GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7
hitectures"
would be unusual enough to justify doing something different. All I am
wondering (from my position of ignorance!) if in this case, perhaps the tests
that cause the circular dependency can be disabled or xfailed, with the
remaining tests run as normal.
cheers
Stuart
--
Stuart Presc
w that you've
laid the ground work. (I hope to do so…)
cheers
Stuart
--
Stuart Prescotthttp://www.nanonanonano.net/ stu...@nanonanonano.net
Debian Developer http://www.debian.org/ stu...@debian.org
GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7
tion to upstream documentation and knows this
story already; at the risk of hijacking this thread, I'd be interested in
the thoughts of others on this.
cheers
Stuart
--
Stuart Prescotthttp://www.nanonanonano.net/ stu...@nanonanonano.net
Debian Developer http://www.debian.org/
[ Resending because I originally sent it to the ghost-town alioth list; this
package is in DMPT but has no active human maintainers. Patches are at
https://bugs.debian.org/866454 ]
On Friday, 19 January 2018 01:43:42 AEDT Stuart Prescott wrote:
> Dear maintainers of plastex,
>
> On
e
advantage in splitting the two groups. Maybe it's time to have PAPT do the
svn→git transition and put everything in the same debian-python-team?
cheers
Stuart
--
Stuart Prescotthttp://www.nanonanonano.net/ stu...@nanonanonano.net
Debian Developer http://www.debian.org/ stu...@debian.org
GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7
nd others!) missed that would make a rather elaborate
packaging dance preferable to this?
cheers
Stuart
--
Stuart Prescotthttp://www.nanonanonano.net/ stu...@nanonanonano.net
Debian Developer http://www.debian.org/ stu...@debian.org
GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7
both old and new numpy.
These two patches only get the package to compile though. Lintian will then
tell you about other RC bugs that you need to fix prior to upload.
regards
Stuart
--
Stuart Prescotthttp://www.nanonanonano.net/ stu...@nanonanonano.net
Debian Developer http://www.debia
our debian/rules is sufficient to fix that. When
set, that sets HOME to the above directory and the build system for some
reason starts using that.
And no, I can't explain why that is...
There are still 3 test failures; the one I glanced at was a missing build-
dep on python3-networkx (
Looks a lot like at least some of the tests are failing with:
https://wiki.debian.org/ContinuousIntegration/TriagingTips/numpy-1.14-doctests
cheers
Stuart
--
Stuart Prescotthttp://www.nanonanonano.net/ stu...@nanonanonano.net
Debian Developer http://www.debian.org/ stu...@debia
usr/local is what
is needed.
Putting python in other places such as /opt or ~/.local would be fine; even
better still is to use one of the many virtualenv approaches so you're not
even leaking that incompatible interpreter into a user's default
environment.
(see also: please don
oring it seems wrong.
Thanks in advance for your suggestions!
Stuart
(on behalf of the Python BoF at DebConf18)
--
Stuart Prescotthttp://www.nanonanonano.net/ stu...@nanonanonano.net
Debian Developer http://www.debian.org/ stu...@debian.org
GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7
I've read the DPMT policy and agree to it.
regards
Stuart
--
Stuart Prescotthttp://www.nanonanonano.net/ stu...@nanonanonano.net
Debian Developer http://www.debian.org/ stu...@debian.org
GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7
ers may have already done so.
If there are questions, please ask for help on IRC #debian-python, or
the debian-python@lists.debian.org mailing list.
--
Stuart Prescotthttp://www.nanonanonano.net/ stu...@nanonanonano.net
Debian Developer http://www.debian.org/ stu...@debian
?
cheers
Stuart
--
Stuart Prescotthttp://www.nanonanonano.net/ stu...@nanonanonano.net
Debian Developer http://www.debian.org/ stu...@debian.org
GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7
need to look for an additional dh step to be added to our normal sequence
to help us with what is becoming a common task?
regards
Stuart
--
Stuart Prescotthttp://www.nanonanonano.net/ stu...@nanonanonano.net
Debian Developer http://www.debian.org/ stu...@debian.org
GPG fingerpri
checked that this is indeed the problem, but patching setup.py to
have instead
license="BSD",
would be the next thing I'd try.
Incidentally, I see that upstream for cogent has ripped out setup.py entirely
and now has a flit based build system which will require a few changes to th
ready to upload.
It's not perfect but seems like a step forward. Thoughts?
cheers
Stuart
--
Stuart Prescotthttp://www.nanonanonano.net/ stu...@nanonanonano.net
Debian Developer http://www.debian.org/ stu...@debian.org
GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7
ends (and Build-Conflicts)
satisfied, and pybuild + the build-backend dependencies are involved in
the cleaning step.
cheers
Stuart
--
Stuart Prescotthttp://www.nanonanonano.net/ stu...@nanonanonano.net
Debian Developer http://www.debian.org/ stu...@debian.org
GPG fingerprint90E2
Hi Scott
On 01/12/2022 15:16, Scott Kitterman wrote:
On Wednesday, November 30, 2022 10:38:30 PM EST Stuart Prescott wrote:
Hi Scott,
On 01/12/2022 02:16, Scott Kitterman wrote:
Package: lintian
Version: 2.115.3
Severity: normal
X-Debbugs-Cc: debian-python@lists.debian.org
The missing
s somewhere in amongst some boost macros associated with initialising
the extension. I didn't actually manage to isolate the issue, however.
Is there a wider problem with boost python that needs addressing perhaps?
regards
Stuart
--
Stuart Prescott http://www.nanonanonano.net/ stu...
Package: libboost-python1.74-dev
Version: 1.74.0-17+b2
Severity: serious
Tags: patch
Justification: Breaks reverse dependencies with Python 3.11
X-Debbugs-Cc: stu...@debian.org, debian-python@lists.debian.org
Dear Maintainer,
Python 3.11 has changed some details around types and GC; boost's enum
, the MBF text should have a note that this will not
become serious before the release of bookworm. (Do we know if that is true?)
cheers
Stuart
--
Stuart Prescott http://www.nanonanonano.net/ stu...@nanonanonano.net
Debian Developer http://www.debian.org/ stu...@debian.org
GPG fingerprint 90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7
e that requirement, the entry points script can
fail at run time for the user. («python3-foo (= ${binary:Version})»
should be ok for packages that are only arch:all).
cheers
Stuart
--
Stuart Prescott http://www.nanonanonano.net/ stu...@nanonanonano.net
Debian Developer http://www.debian.org/ st
some packages (like poetry) ship
egg-info files that are part of the test suite and so are not
regenerated... and they should not be deleted. That's the next task.
regards
Stuart
--
Stuart Prescott http://www.nanonanonano.net/ stu...@nanonanonano.net
Debian Developer http://www.debian.o
tests that we'd really like to
get here. A rebuild test might find more, although code that touches GUI
elements (like plots) tends to be rather under-done in its tests.
regards
Stuart
--
Stuart Prescott http://www.nanonanonano.net/ stu...@nanonanonano.net
Debian Developer http://www.d
ible with matplotlib
3.10 and yet no flags from any tests are coming up. Like many uses of
matplotlib, it probably doesn't even have tests that actually touch the
failing code.
cheers
Stuart
--
Stuart Prescott http://www.nanonanonano.net/ stu...@nanonanonano.net
Debian Develope
thing that lintian will point out if you run it against the .changes file)
That also means that these changes haven't fixed the underlying issue:
CI for 2025.03.1-2 is still failing on multiple architectures (and there
are no changes in 2025.03.1-3).
regards
Stuart
--
Stuart Presc
o
sid prior to thinking about 3.10... but yes, let's look at 3.10 in
experimental immediately after.
regards
Stuart
--
Stuart Prescott http://www.nanonanonano.net/ stu...@nanonanonano.net
Debian Developer http://www.debian.org/ stu...@debian.org
GPG fingerprint 90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7
48 matches
Mail list logo