RFS: dtflickr

[Douglas Thrift]

Dear mentors,

I am looking for a sponsor for my package "dtflickr".

* Package name: dtflickr
 Version : 1.4-1
 Upstream Author : Douglas Thrift 
* URL : http://code.douglasthrift.net/trac/dtflickr
* License : Apache 2.0
 Section : python

It builds these binary packages:
python-dtflickr - Spiffy Flickr API library using JSON

The package appears to be lintian clean.

The upload would fix these bugs: 544643

The package can be found on mentors.debian.net:
- URL: http://mentors.debian.net/debian/pool/main/d/dtflickr
- Source repository: deb-src http://mentors.debian.net/debian unstable main 
contrib non-free
- dget 
http://mentors.debian.net/debian/pool/main/d/dtflickr/dtflickr_1.4-1.dsc


I would be glad if someone uploaded this package for me.

Thanks!

Douglas William Thrift




--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: VCS for Python code Was: Trac team almost dead?

[Nicolas Chauvat]

Hi,

On Wed, Sep 02, 2009 at 12:15:44AM +0800, Chow Loong Jin wrote:
> Git has #1, by the way, if I'm understanding you correctly. Which means both
> ...
> In my case, the more I read about Mercurial, the more I dislike it, but 
> that's a
> different matter.

I'm not sure anyone cares, but at Logilab we have been happy users of
Mercurial for several years now. My bet is that git and hg are the two
dvcs that will survive the current crunch that follows the vcs
explosion which happened a few years ago.

And Mercurial being written in Python makes it easier to hack into it
when needed.

-- 
Nicolas Chauvat

logilab.fr - services en informatique scientifique et gestion de connaissances  


-- 
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: VCS for Python code Was: Trac team almost dead?

[Guy Hulbert]

On Tue, 2009-01-09 at 19:10 +0300, anatoly techtonik wrote:
> On Tue, Sep 1, 2009 at 4:16 PM, Dmitrijs
> Ledkovs wrote:
> > Recently I have discovered some very nice features of hg that make it
> > attractive:
> 
> Mercurial Queues are awesome, but there is one major drawback in
> Mercurial comparing to SVN - it is impossible to clone a subtree of

This drawback is part of the design of git (and mercurial).  It's well
worth viewing linus' 70 minute google video to understand the design
goals and issues.

> repository. In SVN you may checkout any path and isolate your work
> inside. I personally found this feature along with --set-depth option
[snip]

-- 
--gh



-- 
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: VCS for Python code Was: Trac team almost dead?

[Chow Loong Jin]

On Tuesday 01,September,2009 09:16 PM, Dmitrijs Ledkovs wrote:
> Recently I have discovered some very nice features of hg that make it
> attractive:
> 
> 1) Multiple branches such that debian/ can be kept on alioth and have
> working copy that has everything if maintainer prefers so
> 2) MercurialQueues plugin allows to keep versioned quilt patches,
> rebase, merge and split them. Keep their history in a seperate branch
> and always upto date series file.
> 
> This 2 features are very neat that imho bzr and git are lacking. (well
> bzr will have stable support for nested trees soon can be simulated
> with checkouts now and git has tg2quilt)

Git has #1, by the way, if I'm understanding you correctly. Which means both
said features are present in Git at the very least. Also, Git does seem like a
more popular option than Mercurial, so I think going Git would be a better
choice, or many of us and potential newcomers would have to learn a new tool
which they may potentially disagree with.

In my case, the more I read about Mercurial, the more I dislike it, but that's a
different matter.

-- 
Kind regards,
Chow Loong Jin



signature.asc
Description: OpenPGP digital signature

Re: VCS for Python code Was: Trac team almost dead?

[anatoly techtonik]

On Tue, Sep 1, 2009 at 4:16 PM, Dmitrijs
Ledkovs wrote:
> Recently I have discovered some very nice features of hg that make it
> attractive:

Mercurial Queues are awesome, but there is one major drawback in
Mercurial comparing to SVN - it is impossible to clone a subtree of
repository. In SVN you may checkout any path and isolate your work
inside. I personally found this feature along with --set-depth option
very convenient when working with parts of such big projects as Debian
or Python.

There is forest extension and experimental subrepository support in
HG, but it works like svn:externals replacement.

Ciao,
-- 
anatoly t.


-- 
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: VCS for Python code Was: Trac team almost dead?

[Dmitrijs Ledkovs]

Recently I have discovered some very nice features of hg that make it
attractive:

1) Multiple branches such that debian/ can be kept on alioth and have
working copy that has everything if maintainer prefers so
2) MercurialQueues plugin allows to keep versioned quilt patches,
rebase, merge and split them. Keep their history in a seperate branch
and always upto date series file.

This 2 features are very neat that imho bzr and git are lacking. (well
bzr will have stable support for nested trees soon can be simulated
with checkouts now and git has tg2quilt)

One major drawback of hg is missing pristine-tar support and abandoned
hg-buildpackage. Anyone willing to start working on this drawback
together with me? I have a little bit of ugly hackish code.  =)


-- 
With best regards


Dmitrijs Ledkovs (for short Dima),
Ледков Дмитрий Юрьевич


--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: python-support source repository

[anatoly techtonik]

Thank you. Next time I'll try to contact directly. I presumed that
tools like python-support should have a well-known location somewhere
under Python teams repository trees. I've checked all Debian Python
projects with no traces of it. SVN/ViewVC links from the PTS page at
http://packages.qa.debian.org/p/python-support.html are all broken.

Added link to python-support README to http://wiki.debian.org/DebianPythonFAQ

Ciao,
--anatoly t.



2009/9/1 Josselin Mouette :
> Le mardi 01 septembre 2009 à 13:53 +0300, anatoly techtonik a écrit :
>> Can anybody point me to the repository location of python-support package?
>
> It’s in collab-maint :
> http://svn.debian.org/viewsvn/collab-maint/deb-maint/python-support/trunk/
>
> Cheers,
> --
>  .''`.      Josselin Mouette
> : :' :
> `. `'   “I recommend you to learn English in hope that you in
>  `-     future understand things”  -- Jörg Schilling
>


--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: python-support source repository

[Josselin Mouette]

Le mardi 01 septembre 2009 à 13:53 +0300, anatoly techtonik a écrit : 
> Can anybody point me to the repository location of python-support package?

It’s in collab-maint :
http://svn.debian.org/viewsvn/collab-maint/deb-maint/python-support/trunk/

Cheers,
-- 
 .''`.  Josselin Mouette
: :' :
`. `'   “I recommend you to learn English in hope that you in
  `- future understand things”  -- Jörg Schilling


signature.asc
Description: Ceci est une partie de message numériquement signée

Re: python-support source repository

[Sandro Tosi]

On Tue, Sep 1, 2009 at 12:53, anatoly techtonik wrote:
> Hello,
>
> Can anybody point me to the repository location of python-support package?

You should ask the maintainer of the package, since we are "users" of
it. I've added Joss in CC, python-support developer and maintainer.

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi


-- 
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: Endianness detection change on numpy

[Kumar Appaiah]

On Mon, Aug 31, 2009 at 03:59:33PM -0400, Aaron M. Ucko wrote:
> Kumar Appaiah  writes:
> 
> > The fix is simple: either their new npy_endian.h method is broken,
> > since it does not attempt to find the endian.h present on all Debian
> > machines, or I have not figured out how to force the use of
> > endian.h. A simple workaround I'd suggest is to path the npy_endian.h
> > provided to force the use of endian.h, for that is the most general
> > way and sure to work on all Debian systems. However, before resorting
> > to patching, I wanted know if someone can suggest a more elegant
> > method to get around this problem, which I haven't been able to figure
> > out.
> 
> In general, it's fine to assume endian.h on Debian.  For broader
> portability, though, I'd add the following suggestions to the one from
> #544291:
> 
> - Fix numpy's build system to #define NPY_HAVE_ENDIAN_H as
>   appropriate, and npy_endian.h to #include "numpyconfig.h".
> 
> - Per pyconfig.h, take advantage of the fact that GCC predefines
>   __BIG_ENDIAN__ or __LITTLE_ENDIAN__ as appropriate.  (Numpy's
>   headers shouldn't actually #include , of course, just
>   learn from it.)
> 
> - Fall back on trying  rather than #error-ing out, on the
>   grounds that a possible error is better than a guaranteed one.

Thanks Aaron. I'll let upstream know of this.

Kumar
-- 
Kumar Appaiah


-- 
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

python-support source repository

[anatoly techtonik]

Hello,

Can anybody point me to the repository location of python-support package?

Thanks.

--anatoly t.


-- 
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: Trac - DPMT or PAPT?

[Piotr Ożarowski]

[W. Martin Borgert, 2009-09-01]
> sorry for bringing up this again: Is it OK to put Trac into
> PAPT, not into DPMT? Reason: I think Trac and at least some
> of it's plugins should be maintained together (same team,
> same VCS, Trac users know too well the problem of plugins
> not fitting in a specific Trac version...), so this is
> "application" stuff, not "library"/"module".

it's OK (IMHO)
-- 
-=[ Piotr Ożarowski ]=-
-=[ http://www.ozarowski.pl ]=-


-- 
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Trac - DPMT or PAPT?

[W. Martin Borgert]

Hi,

sorry for bringing up this again: Is it OK to put Trac into
PAPT, not into DPMT? Reason: I think Trac and at least some
of it's plugins should be maintained together (same team,
same VCS, Trac users know too well the problem of plugins
not fitting in a specific Trac version...), so this is
"application" stuff, not "library"/"module".

Cheers


-- 
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: python-sqlkit or sqlkit?

[Seo Sanghyeon]

2009/9/1 Alessandro Dentella :
>  At the moment the debian package is named 'python-sqlkit' and also
>  provides the script/application named 'sqledit', but I'm not sure that
>  this is the correct/best approach.

I think this is okay.

>  Should I split it into different packages? Clearly sqlkit is a public
>  package.

And I don't think split is needed.

-- 
Seo Sanghyeon


--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

python-sqlkit or sqlkit?

[Alessandro Dentella]

Hi,

  I have a pure python package 'sqlkit' that provides PyGTK Widgets to
  edit data in a database. Source code is about 1.5 MB.

  In the package I also provide an application that is a little script (12
  KB) that is a GUI to edit databases that clearly is based on sqlkit the
  module. 

  At the moment the debian package is named 'python-sqlkit' and also
  provides the script/application named 'sqledit', but I'm not sure that
  this is the correct/best approach.
   
  Should I split it into different packages? Clearly sqlkit is a public
  package.

  any hints?
  sandro
  *:-)


-- 
Sandro Dentella  *:-)
http://sqlkit.argolinux.orgSQLkit home page - PyGTK/python/sqlalchemy


-- 
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org