On Thu, 28 Jan 2010, Cyril Brulebois wrote:
> > So you have/had no plans to prepare new upload.  Fresh upload might
> > not be of any importance for you, but it is important for me and
> > nipype users.
> Not that it matters much, but it's usually considered polite not to
> quote private conversations unless otherwise specified.
my sincere apologies -- I could have been more polite indeed

> so that it can be made sure they don't break existing
> stuff. -networkx belongs to that category, and it's going to stay
> there until I'm confident with it.
yeah -- aging had proved to make cheeses tastier ...

The only other packages besides nipype which depend on networkx atm is sagemath
of some old release and python-sasync, so I would not expect any "grave damage"
to the system although indeed some functionality within sage might break.

Now lets look on how good old 0.99 was/is in respect to be kind to those
rdepends:


,-------------------------------------------------------------------------------------
| In [1]: import sasync.graph
| /usr/lib/pymodules/python2.5/matplotlib/numerix/__init__.py:18: 
DeprecationWarning:
| **********************************************************
| matplotlib.numerix and all its subpackages are deprecated.
| They will be removed soon.  Please use numpy instead.
| **********************************************************
|
|   warnings.warn(msg, DeprecationWarning)
| ---------------------------------------------------------------------------
| AttributeError                            Traceback (most recent call last)
|
| /home/yoh/<ipython console> in <module>()
|
| /usr/lib/pymodules/python2.5/sasync/graph.py in <module>()
|     204
|     205
| --> 206 class XGraph(_Persistent, NX.XGraph):
|     207     """
|     208     Persistent version of L{NX.XGraph}
|
| AttributeError: 'module' object has no attribute 'XGraph'
`---
and that is with networkx 0.99 .  

sagemath seems to think that it still uses 0.36 so, once again, 0.99 isn't a 
good fit:

,---
| $> python -c 'import networkx; print networkx.__version__; networkx.XDiGraph'
| /usr/lib/pymodules/python2.5/matplotlib/numerix/__init__.py:18: 
DeprecationWarning:
| **********************************************************
| matplotlib.numerix and all its subpackages are deprecated.
| They will be removed soon.  Please use numpy instead.
| **********************************************************
|
|   warnings.warn(msg, DeprecationWarning)
| 0.99
| Traceback (most recent call last):
|   File "<string>", line 1, in <module>
| AttributeError: 'module' object has no attribute 'XDiGraph'
`---

So, apparently both other packages which depend on networkx are currently
broken and any system is as in bad shape with current version as it would be
with new version of networkx 1.0.1.  Actually probably it is in the worse shape
since probably 1.0.1 has addressed some bugs since 0.99, and from what I
remember upstream has aged this release for a while as well!

So, once again, any objective reason besides desire to "age" it a bit?  Or do
you have some private stress-testing battery for python-networkx?


> Poor poor poor users. Guess what, experimental is for stuff not fully
> tested

what document said that?  I thought that 'unstable' is exactly for that
purpose.

Contrary (emphasis are mine), debian dev ref says:
,---
| 4.6.4.3. Experimental
|
|  If there is a chance that the software could do *grave damage* to a
|  system, it is likely to be better to put it into experimental.
|  ...
|  New software which isn't likely to damage your system can go directly into 
unstable.
`---

Indeed it doesn't say 'should' but 'could'

debian policy (footnote 35) says:

,---
|  unstable
|
|     This distribution value refers to the developmental part of the
|     Debian distribution tree. Most new packages, *new upstream versions* of 
packages
|     and bug fixes go into the unstable directory tree.
|
| experimental
|
|     The packages with this distribution value are deemed by their
|     maintainers to be *high risk*. Oftentimes they represent early beta or
|     developmental packages from various sources that the maintainers want 
people to
|     try, but are not ready to be a part of the other parts of the Debian
|     distribution tree.
`---

so, sure, everything is up to your discretion, but please be considerate.



> > Not to mention that nipype remains outside of the candidates to be
> > included in the next Debian release.
> Freeze isn't tomorrow, or next week, unless I'm mistaken.
I love arguments toward doing everything the last day

-- 
                                  .-.
=------------------------------   /v\  ----------------------------=
Keep in touch                    // \\     (yoh@|www.)onerussian.com
Yaroslav Halchenko              /(   )\               ICQ#: 60653192
                   Linux User    ^^-^^    [175555]


Attachment: signature.asc
Description: Digital signature

Reply via email to