Re: Django 1.7 preparations

I think the following bug I just noticed is significant. Unless fixed, it means that after Django 1.7 is released Debian won't have a Mysql library for it that works with Python3. https://bugs.debian.org/758844 http://bugs.mysql.com/bug.php?id=72542 -- Brian May br...@microcomaustralia.com.au

Re: guardian and django1.7

As an experiment, I imported django-guardian from the *.dsc files to git using git-dpm, and applied my changes. Not sure if I have got this right, it was the first time I used git-dpm. The result is currently at: https://github.com/brianmay/django-guardian/tree/patched (patched branch). This is

Re: Django 1.7 preparations

On 22 August 2014 09:49, Brian May br...@microcomaustralia.com.au wrote: I think the following bug I just noticed is significant. Unless fixed, it means that after Django 1.7 is released Debian won't have a Mysql library for it that works with Python3. https://bugs.debian.org/758844 http

Re: guardian and django1.7

On 25 August 2014 15:50, Brian May br...@microcomaustralia.com.au wrote: At the moment, am wondering if maybe this is a Django 1.7 bug. Unless I hear otherwise, I am going to assume this is a Django 1.7 bug: https://code.djangoproject.com/ticket/23360 -- Brian May br

Re: guardian and django1.7

of the problems. e.g. https://github.com/brianmay/django-guardian/blob/master/debian/patches/0008-Fix-conflicting-related_name.patch -- Brian May br...@microcomaustralia.com.au

Re: Proposed git migration plan

, these are the ones that have annoyed me recently. Unlike some, I am happy to continue using subversion. However I feel I could do a better, more professional job with git. -- Brian May br...@microcomaustralia.com.au

Re: Update to Veusz 1.21.1

modules, of course), although I don't know enough about veusz to say whether this is the case or not. Also, if is an application (as opposed to module/library), there is probably no point packaging both Python3 and Python2 versions. Pick one, and package that. -- Brian May br

Re: Django 1.7 preparations

On 22 August 2014 09:49, Brian May br...@microcomaustralia.com.au wrote: I think the following bug I just noticed is significant. Unless fixed, it means that after Django 1.7 is released Debian won't have a Mysql library for it that works with Python3. https://bugs.debian.org/758844 http

Re: python-openssl unavailable in sid

didn't respond, maybe it come good by itself? -- Brian May br...@microcomaustralia.com.au

django 1.7 change for backport to wheezy

% confident of the branches - I guess I should use the debian/experimental branch? Thanks -- Brian May br...@microcomaustralia.com.au

django 1.7 migrations

Python 3. Presumably if you use unicode strings everywhere or add the following to the top of model files, this wouldn't be an issue. Not tested it myself. from __future__ import unicode_literals I reported this upstream: https://code.djangoproject.com/ticket/23455 Thanks -- Brian May br

Fwd: Processed: not a django1.7 bug

-- Forwarded message -- From: Debian Bug Tracking System ow...@bugs.debian.org Date: 9 September 2014 16:06 Subject: Processed: not a django1.7 bug To: Brian May br...@microcomaustralia.com.au Processing commands for cont...@bugs.debian.org: user python-dja...@packages.debian.org

Re: django 1.7 change for backport to wheezy

, easy to redo it. -- Brian May br...@microcomaustralia.com.au

django / python-mysql.connector / python2 / unicode broken

for Django1.6, I only have tested 1.7 myself. -- Brian May br...@microcomaustralia.com.au

Re: Help needed to test packages with Django 1.7

On 7 August 2014 10:19, Brian May br...@microcomaustralia.com.au wrote: virtualenv --system-site-packages ~/old_django . ~/old_django/bin/activate pip install django==1.6.5 pip install django-south django-admin --settings=??? migrate --all Calling django-admin like that won't use

Re: Help needed to test packages with Django 1.7

Python 2.6 stuff that is no longer relevant, as Python2.6 isn't supported any more. Will remove this too. -- Brian May br...@microcomaustralia.com.au

django 1.7 bugs

it works with Django 1.7 Bugs forwarded upstream (may not get fixed in time for the freeze): #755585 [i| |↝] [src:dico] dico: Please ensure it works with Django 1.7 #755667 [i| |↝] [src:django-openid-auth] django-openid-auth: Please ensure it works with Django 1.7 -- Brian May br

Re: django 1.7 bugs

with Django 1.7 (e.g. if a Python Team module depends on a non-python team module). I see you remembered to CC Raphael Hertzog - thanks for that; I totally forgot. -- Brian May br...@microcomaustralia.com.au

Re: Help needed to test packages with Django 1.7

On 11 September 2014 16:39, Brian May br...@microcomaustralia.com.au wrote: Ok, will look into this tomorrow. Just pushed a change. Unfortunately, had problems testing this because debian/rules clean removes Django.egg-info/* which is flagged by git-buildpackage as uncommitted changes. Also

Re: How to solve #751375, file clash

the file supplied by python-configparser? If it is the same file, you could delete it from python-pies2overrides and depend on python-configparser. -- Brian May br...@microcomaustralia.com.au

Bug#770779: unblock: python-django-guardian/1.2.4-2

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock python-django-guardian was RC bug #763222. I believe this is a just a technical bug in the tests, the actual package should work fine. However, it means the package won't build. This in

multiple modules in one source

everything combined, or maybe trying to convincing upstream that they shouldn't combine the (very much related) modules into one source. (at the present it is still very much alpha and no released version yet) Thanks -- Brian May br...@microcomaustralia.com.au

Re: multiple modules in one source

On 12 December 2014 at 09:48, Ben Finney ben+deb...@benfinney.id.au wrote: Just about any non-trivial Python package (and some trivial ones) in Debian will have many distinct modules. Possibly I am getting my terminology confused. You're familiar with ‘python-django’, as just one example.

Re: multiple modules in one source

now. -- Brian May br...@microcomaustralia.com.au

dh_python2 missing

in came good. Not entirely sure this is a bug that needs to be reported, however letting other people know just in case this isn't something unique to be setup on this particular computer. Thanks -- Brian May br...@microcomaustralia.com.au

Bug#778269: ITP: python-mkdocs -- Static site generator geared towards building project documentation

Package: wnpp Severity: wishlist Owner: Brian May b...@debian.org * Package name: python-mkdocs Version : 0.11.1 Upstream Author : Tom Christie * URL : http://www.mkdocs.org/ * License : BSD Programming Lang: Python Description : Static site generator

Re: Bug#778269: ITP: python-mkdocs -- Static site generator geared towards building project documentation

2.5 is for Python 2.6 support, which we don't care about. -- Brian May b...@debian.org

Re: Bug#778269: ITP: python-mkdocs -- Static site generator geared towards building project documentation

On 14 February 2015 at 09:52, Brian May b...@debian.org 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

Re: Build separate binary packages from single source

-server http://pypi.python.org/pypi/devpi-web http://pypi.python.org/pypi/devpi-client As each one has its own version number, and presumably its own release cycle, presumably you should be packaging them as separate Debian source packages. -- Brian May br...@microcomaustralia.com.au

Re: [Python-modules-team] Bug#782756: should not be in Section: python

On Mon, 20 Apr 2015 at 10:44 Ben Finney ben+deb...@benfinney.id.au wrote: What does the package primarily install? Would you characterise the work's purpose as: * web: “Web servers, browsers, proxies, download tools etc.” Doesn't seem applicable, it doesn't do anything with HTTP. * utils:

Re: [Python-modules-team] Bug#782756: should not be in Section: python

On Tue, 21 Apr 2015 at 14:38 Damyan Ivanov d...@debian.org wrote: Its description says static site generator. Sounds a lot like HTTP to me, not less than ikiwiki for example. I think you might be getting HTTP confused with HTML. Both ikiwiki and mkdocs turn files into static HTML files, but

Re: python3-xlib lost in Debian

On Mon, 27 Apr 2015 at 12:26 mudongliang mudonglianga...@hotmail.com wrote: Today I try to install a software - youdao dict. First I try it in vmware machine: Linuxmint and Ubuntu. It can succeed! But when I do it in Debian , it fails ; And the reason is the lost of python3-xlib. So I search

Re: Bug#785275: ITP: python-ipaddress -- Backport of the ipaddress module from Python 3.3

On Fri, 22 May 2015 at 07:14 Scott Kitterman deb...@kitterman.com wrote: I was considering the idea of porting things from ipaddr to ipaddress for python2, but there's a lot more of that then there is for ipaddress (which is up to only two packages we know about). As it is a goal to have

Bug#794829: ITP: python-django-cors-headers -- Django app for handling the server headers required for Cross-Origin Resource Sharing (CORS)

Package: wnpp Severity: wishlist Owner: Brian May b...@debian.org * Package name: python-django-cors-headers Version : 1.1.0 Upstream Author : Otto Yiu * URL : https://github.com/ottoyiu/django-cors-headers/ * License : MIT Programming Lang: Python2

Re: Bug#802839: django-celery: python 3 tests not invoked and break

to think about if it is worth fixing, and what the best fix is. -- Brian May <b...@debian.org>

Re: git-dpm: ERROR: 'upstream' does not contain previously recorded revision

s As sometimes "git push --all" won't push the tags - I think it won't push the tag if the changeset is already on the server. -- Brian May <b...@debian.org>

Re: Git migration schedule

Sandro Tosi <sandro.t...@gmail.com> writes: > On Wed, Oct 21, 2015 at 11:01 PM, Brian May <b...@debian.org> wrote: >> Maybe we should fix #801666 first and then revisit this question? > > git-dpm hasnt seen a single line changed since more than a year > (http://anons

Bug#802727: ITP: pytest-django -- Test Django project/applications with pytest.

Package: wnpp Severity: wishlist Owner: Brian May <b...@debian.org> * Package name: pytest-django Version : 2.9.1 Upstream Author : Andreas Pelme * URL : https://github.com/pytest-dev/pytest-django * License : BSD Programming Lang: Python 2 and Py

Bug#802730: ITP: python-setuptools-scm -- Handles managing your python package versions in scm metadata.

Package: wnpp Severity: wishlist Owner: Brian May <b...@debian.org> * Package name: python-setuptools-scm Version : 1.8.0 Upstream Author : Ronny Pfannschmidt * URL : https://github.com/pypa/setuptools_scm/ * License : MIT Programming Lang: Py

Re: [Python-modules-team] Bug#803117: celery: non-free documentation (CC-BY-NC-SA-3.0)

e source to drop the entire docs directory and remove the python-celery-doc package :-( -- Brian May <b...@debian.org>

Re: Bug#802839: django-celery: python 3 tests not invoked and break

Brian May <b...@debian.org> writes: > == > FAIL: test_discovery_with_broken (djcelery.tests.test_discovery.TestDiscovery) > -- > Traceback (mos

Re: git-dpm: ERROR: 'upstream' does not contain previously recorded revision

tag > git-dpm: ERROR: 'upstream' differs from recorded one! This is a known bug with git-dpm. See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801548. Until it is fixed, the best work around seems to be to create the tags manually, at least until you import a new upstream version. Then the problem will go away. -- Brian May <b...@debian.org>

pytest

eem to initialize Django properly (it works when called by tox, not sure what the difference is). So what is going wrong, and what is the solution? Thanks -- Brian May <b...@debian.org>

Re: Git migration schedule

nd then revisit this question? -- Brian May <b...@debian.org>

Re: pypi.debian.net offline?

Thomas Goirand <z...@debian.org> writes: > On 11/11/2015 07:56 AM, Brian May wrote: > Please be patient. It should be up by tomorrow at least. Something went wrong with it? -- Brian May <b...@debian.org>

Re: Request to join DPMT && python-django-registration

't see the subject line, and he said django in the body, not python-django-registration. Which got me confused, as python-django has no RC bugs. -- Brian May <b...@debian.org>

Re: pypi.debian.net offline?

Thomas Goirand <z...@debian.org> writes: > FYI, here's what happened. [...] Thanks for the detailed explanation. Good that it is back again. -- Brian May <b...@debian.org>

Re: Request to join DPMT && python-django-registration

Stephan Sürken <abs...@debian.org> writes: > As first urgent quest I would like to fix the RC django 1.8 (I already > did some work on that package for some time before it was moved to the > DPMT). I am not sure what you are referring to here? -- Brian May <b...@debian.org>

Re: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental

On Thu, 8 Oct 2015 at 00:32 Thomas Goirand wrote: > You've only enforced *your own* policy, backed-up by only a small vocal > minority, taking the rule to the extreme (ie: a few days before the Git > migration, it's still not ok to start new projects using Git, according > to

Python < 3.5 tests

Hello, When debugging #801208, I noticed the following output: dh_auto_test -O--buildsystem=pybuild I: pybuild base:170: cd /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build; python2.7 -m unittest discover -v -- Ran 0

Re: Git migration schedule

lem with using master instead of debian/master, unless you want to maintain seperate branches for Ubuntu and Debian packages (a level of complexity I prefer not to think too much about right now...) -- Brian May <b...@debian.org>

Re: Python Policy

les.git and http://python-modules.alioth.debian.org/? -- Brian May <b...@debian.org>

Re: Python Policy

ython interpreter." There are packages that do not provide public modules that are aimed at developers. I imagine there are also packages that are end user applications that do provide public modules, for end user programming. These end user's may require the first group of packages aimed at developers too. -- Brian May <b...@debian.org>

Re: Python Policy

ps://github.com/bradleyayers/django-tables2/issues/267 I probably will end up using github source - and I suspect that is what I have done in the past - debian/watch points to Pypi - something else I will need to fix too, I guess. -- Brian May <br...@microcomaustralia.com.au>

Re: git instead of svn in DPMT policy

to a non-master branch? e.g. post-git-migrate? As a first step, I would suggest deleting the entire "Subversion Procedures" section. Maybe it could be replaced by a "Git Procedures" section that has a link to the wiki page? https://wiki.debian.org/Python/GitPackaging -- Brian May <br...@microcomaustralia.com.au>

Re: [Python-modules-team] django-ajax-selects is marked for autoremoval from testing

Hello, Can somebody please explain this email? I know it says 2015-11-05, but looks like it was sent today. As far as I can tell version 1.3.6-4 is in testing (not 1.3.6-3 as per message), it got into testing 5 days ago, and this version has closed the bug. Is this something I have to worry

Re: [Python-modules-team] django-ajax-selects is marked for autoremoval from testing

On Thu, 15 Oct 2015 at 15:50 Brian May <br...@microcomaustralia.com.au> wrote: > As far as I can tell version 1.3.6-4 is in testing (not 1.3.6-3 as per > message), it got into testing 5 days ago, and this version has closed the > bug. > Actually, I may have misread that.

Re: Python < 3.5 tests

On Thu, 8 Oct 2015 at 22:44 Dmitry Shachnev wrote: > Python 3.4 is still the default version in Debian. We can't do the switch > at once, so the transition is split into three steps: > > 1) Add Python 3.5; > 2) Make 3.5 the default; > 3) Remove Python 3.4. > > We are

Re: Python < 3.5 tests

On Thu, 8 Oct 2015 at 22:44 Dmitry Shachnev wrote: > > There was a change in unittest autoloader in Python 3.5. It now tries to > import the package even if it has no tests. I do not know if it is an > intended change, or a side-effect of fixing some bug ([1]?). Maybe Robert

Re: Python < 3.5 tests

On Fri, 9 Oct 2015 at 08:16 Robert Collins wrote: > But - ajax_select/__init__.py is going to be imported, and thats whats > erroring. I don't think that this is a 3.5 unit testing change - I > think its an error importing some bit of django. > On 2nd thoughts, I

Re: Python < 3.5 tests

On Fri, 9 Oct 2015 at 08:49 Robert Collins wrote: > The reason it's being discovered is likely due to the pattern bugfix > (also in 3.5) - previously discover couldn't handle directories with > names tht didn't match the file pattern - and that meant nested test >

Re: Git migration schedule

On Fri, 9 Oct 2015 at 02:06 Stefano Rivera wrote: > Done. And kicking off the migration now... > Great! Will the migration do packages like python-django? Just thinking that python-django in subversion is old, and the version in git doesn't (yet) use git-dpm; you don't

Re: python-django

On Sat, 10 Oct 2015 at 09:54 Brian May <br...@microcomaustralia.com.au> wrote: > We can move the migrated version out of the way, restore the old version, > and update it to the required standards (e.g. git-dpm). Is everyone happy > with this approach? > Have moved the repos

Re: tagging releases in git

On Sun, 11 Oct 2015 at 10:42 Barry Warsaw wrote: > What I've done, and it's probably horrible, is to just `git-dpm tag > --refresh` > and then `git push --tags --force`. > That does look yuck. If my vague understanding is correct, it seems that git-dpm wants to assign the

Re: python-django

On Sun, 11 Oct 2015 at 13:50 Brian May <br...@microcomaustralia.com.au> wrote: > I just converted and pushed these branches to git-dpm. > > Just noticed how it named the upstream branches. * [new branch] upstream-debian/experimental -> upstream-debian/experimental * [new branc

Re: python-django

On Sun, 11 Oct 2015 at 11:40 Brian May <br...@microcomaustralia.com.au> wrote: > Should we convert all branches to git-dpm? Or forget the branches > referring to obsolete distributions? > > Probably should do these: > > origin/debian/experimental > origin/debian/jess

Bug#801548: git-dpm: tag 'upstream/*' already exists and differs!

Package: git-dpm Version: 0.9.1-1 Severity: normal Trying to add a tag to an new release of a DPMT migrated package I get the following error: brian@prune:~/tree/debian/python-modules/django-ajax-selects$ git-dpm tag git-dpm: ERROR: tag 'upstream/1.3.6' already exists and differs! To me this

packages missing from https://anonscm.debian.org/cgit/python-modules/packages/

Hello, Why are packages missing from anonscm.debian.org which are on git.debian.org? e.g. https://anonscm.debian.org/cgit/python-modules/packages/django-model-utils.git https://anonscm.debian.org/cgit/python-modules/packages/django-xmlrpc.git I note these packages don't have the required

warnings importing new upstream source

As far as I know this actually did work despite the complaining about no parent commit... What does that mean? git-dpm import-new-upstream --ptc --rebase-patched ../django-model-utils_2.3.1.orig.tar.gz There were no patches recorded, so merging the new state directly (no git-dpm rebase-patched

Re: managing transitions (was: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental)

On Tue, 6 Oct 2015 at 18:46 Thomas Goirand wrote: > This IMO is the same topic as having a Gerrit review system (and not > just Git) which could do tests on each change of a package even before > having them committed to our git. > Sounds like an interesting thing to

Re: Git migration schedule

On Fri, 9 Oct 2015 at 18:58 Stefano Rivera wrote: > It migrated everything that's in SVN. What happens to the result is up > to us. We can replace migrated results with existing git packages. > Ok, I probably should create another thread to discuss this for Django then.

Re: Python < 3.5 tests

On Fri, 9 Oct 2015 at 17:22 Brian May <br...@microcomaustralia.com.au> wrote: > That is the develop branch. So not in any released version, which is the > master branch. > The tests at the moment are somewhat useless too, still need to be written. Think the best solutio

Re: Git migration schedule

On Sat, 3 Oct 2015 at 00:24 Barry Warsaw wrote: > 5-Oct - Do one last test run with an updated svn dump. Put the results in > a > public place for folks to play with and comment on. > > 8-Oct - Assuming no objections or showstoppers, turn off write access to > all > of DPMT

Re: Git migration schedule

On Fri, 9 Oct 2015 at 19:01 Stefano Rivera wrote: > Things that need to be looked at: > http://whiteboard.debian.net/dpmt-git-migration.wb > Not sure what the headings mean. "Git packages moved out the way" seems obvious - and probably exactly what I mentioned before with

Re: Git migration schedule

On Fri, 9 Oct 2015 at 19:26 Stefano Rivera wrote: > > Here: > https://wiki.debian.org/Python/GitPackaging#Where_do_the_team.27s_git_branches_live.3F > > I seem to have problems with this because my username on my local box is "brian" however my username on git.debian.org is

tagging releases in git

According to the wiki I do this with the following command: brian@prune:~/tree/debian/python-modules/django-ajax-selects$ git-dpm tag git-dpm: ERROR: tag 'upstream/1.3.6' already exists and differs! This wasn't the response I was expecting. I am not sure why it is trying to change the upstream

Re: git.debian.org broken link

On Sat, 10 Oct 2015 at 16:43 Scott Kitterman wrote: > http://git.debian.org/?p=python-modules/packages/ redirects to > http://anonscm.debian.org/cgit/python-modules/packages which doesn't show > a > repository for django-ajax-selects, so it looks like it's actually missing.

git.debian.org broken link

When I fixed a bug in git: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801208 It put a link to a diff in the bug report: http://git.debian.org/?p=python-modules/packages/django-ajax-selects.git;a=commitdiff;h=9d026b4 Initially this was coming up with "Internal Server Error". Now it is

Re: git repo lint tool

On Wed, 14 Oct 2015 at 01:31 Stefano Rivera wrote: > python-django: No control file > python-django: Not git-dpmmed > Suspect it might be getting confused with the different branch names used here. At least there was a control file when I looked last :-)

Re: [DPMT] radical changes: automation, carrot and stick

On Mon, 5 Oct 2015 at 08:54 Stefano Rivera wrote: > There's a fundamental question to ask here. Do we want to welcome Python > packages into the team, or do we want to put up barriers and require a > level of commitment before packages can be brought into the team?

Re: Git migration schedule

On Tue, 6 Oct 2015 at 02:49 Barry Warsaw wrote: > Waiting longer isn't an option IMHO. It's helping to add to the > dysfunction > of the team. I will also offer to help if the 3.5 transition gets stuck > because of the git conversion. > Hurry up and break my packages :-) Do

Re: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental

On Tue, 6 Oct 2015 at 09:33 Scott Kitterman wrote: > Except in this case you not only didn't but then got defensive when called > on it. If you'd just reacted with something like "Oops, made a mistake, > I'll > revert it from svn and ask for it to be removed from

Re: Rebuild for packages with entry points?

this problem will be solved. -- Brian May <b...@debian.org>

django-ajax-selects

as such, however lintian has become more strict about such issues, and lintian complains loudly. Any suggestions? -- Brian May <b...@debian.org>

Re: Packages with Django 1.7 issues

Brian May <br...@linuxpenguins.xyz> writes: > At what point do we conclude that nobody is interested in maintaing > these packages (or even just testing the packages) and they should get > removed from Debian unstable? > > https://bugs.debian.org/cgi-bin/pkgreport

Re: [Python-modules-team] My Pip installation is broken after upgrading Debian from oldstable/Wheezy to stable/Jessie...

Sheesh. I also notice it > is an old bug that is still not fixed. :( Are you sure? This bug was supposedly fixed in the Jessie version... -- Brian May <b...@debian.org>

Re: [Python-modules-team] My Pip installation is broken after upgrading Debian from oldstable/Wheezy to stable/Jessie...

es are tested by Debian to work with Debian packages. Just to confuse matters, there are some upstream packages - particular those not yet in Debian, where the upstream authors do recommend installing missing dependancies with "pip install xyz" - this is not actually good practise. Hope this helps. -- Brian May <b...@debian.org>

Bug#810061: ITP: python-django-environ -- utilize 12factor inspired environment variables for Django

Package: wnpp Severity: wishlist Owner: Brian May <b...@debian.org> * Package name: python-django-environ Version : 0.4 Upstream Author : joke2k * URL : https://github.com/joke2k/django-environ/ * License : MIT Programming Lang: Python2 and P

Re: [Python-modules-team] Bug#806334: kombu: FTBFS: ImportError: cannot import name '_uuid_generate_random'

Brian May <b...@debian.org> writes: > Don't think we can complain at Python though, looks like a private > symbol. Looks like this is a work around for a bug that was in Python 2.5. http://bugs.python.org/issue4607: >From kombu code: def uuid4(): # Workaround for http://

Packaging Python that requires 3.5

Apparently this doesn't work just yet. In debian/control I have X-Python3-Version: >= 3.5 This gives in the Depends: python3.5:any, python3:any (>= 3.5~) This cannot be statisfied because python3 the version in unstable is 3.4.3-7 -- Brian May <br...@linuxpenguins.x

Re: [Python-modules-team] Bug#806334: kombu: FTBFS: ImportError: cannot import name '_uuid_generate_random'

ped a symbol that was present in Python 3.5.0. Don't think we can complain at Python though, looks like a private symbol. CCing debian-python list in case anybody else has more information on why _uuid_generate_random disappeared. -- Brian May <b...@debian.org>

Re: Packaging Python that requires 3.5

aiting point is. Is there anything that can be done to help? -- Brian May <b...@debian.org>

Re: Which bug report is tracking the “python3 is Python 3.5” transition? (was: Packaging Python that requires 3.5)

Scott Kitterman <deb...@kitterman.com> writes: > We haven't started the transition yet. When it starts, binNMU should > be enough for most of the packages. When will you start the transition? -- Brian May <b...@debian.org>

Re: Which bug report is tracking the “python3 is Python 3.5” transition? (was: Packaging Python that requires 3.5)

hether they're > waiting on something we can help with. Not that I can see. So maybe that means any of the red packages on the transition tracking page. Some of the packages look like they are broken with no immediate fix, maybe should get removed from unstable *if* inclusion in unstable is holdi

Re: [Python-modules-team] New git repository is not available in git/http protocol

s message too, the python-modules-team address is intended for automatic messages. -- Brian May <br...@linuxpenguins.xyz> https://linuxpenguins.xyz/brian/

nose python3.5 issues

t.py", line 282, in test_addSuccess eq_(tc.attrib['classname'], "test_xunit.TC") AssertionError: 'test_xunit.mktest..TC' != 'test_xunit.TC' >> begin captured stdout << ----- b'' - >> end captured stdout << -- -- Ran 387 tests in 12.394s FAILED (SKIP=18, failures=5) -- Brian May <br...@linuxpenguins.xyz> https://linuxpenguins.xyz/brian/

Re: Any suggested procedure if upstream does not provide any build helper like setup.py

could possible go wong? If I break homebrew (MacOSX packages), that might upset people however. Might try and see if I can test formulas using linuxbrew first. There actually good reasons for upstream to do this, e.g. I think a proper setup.py is a requirement to get packages into PyPI. -- Brian May <b...@debian.org>

Re: [Python-modules-team] python-docker issue?

-===-===-=== ii python-docker 1.5.0-1 all Python wrapper to access docker.io's control socket The "apt-cache show python-docker" shows what version of pyt

Re: mkdocs locale error building djangorestframework

Ben Hutchings <b...@decadent.org.uk> writes: > Oh, well that's probably because you only set LANG and it's being > overridden by LC_ALL.  Use a bigger hammer: set LC_ALL yourself. Yes, somebody mentioned this on the BTS also. I very much suspect this will be the solution. Thanks -

Re: mkdocs locale error building djangorestframework

fatal error message that should get displayed. i.e. we should never have executed this code in the first place. (I did file a bug on the python3 issue however) -- Brian May <b...@debian.org>

<    1   2   3   4   >