Re: [cclib-devel] Moving ccopen

[Karol L. <kar...@gm...>]

Well, if you can change it on your end that would be great.

Perhaps we could agree for the future that the "cclib" namespace will not
change? We can create aliases there that will be updated in case code moves
around again.

For ccopen: https://github.com/cclib/cclib/pull/366

On Fri, Apr 28, 2017 at 10:10 AM, Noel O'Boyle <bao...@gm...> wrote:

> No worries, though if I'm using the API wrongly, then it's something I
> should fix at my end. Maybe I should read the docs now :-)
>
> On 28 April 2017 at 16:22, Karol Langner <kar...@gm...> wrote:
> > Hey Noel,
> >
> > We now have both reading and writing in cclib.io.
> >
> > I'm the perpetrator, and wasn't aware something depended on this. We
> should
> > do a better job of documenting the public API...
> >
> > Looking back, the move was made last year to avoid a circular import,
> when
> > writing some new writers IIRC. I'm sure we can figure out a way around
> this.
> >
> > Could you file an issue for this?
> >
> > - Karol
> >
> >
> > On Fri, Apr 28, 2017 at 5:30 AM, Noel O'Boyle <bao...@gm...>
> wrote:
> >>
> >> Hi there,
> >>
> >> I might be a bit out of the loop, but is there any chance of moving
> >> ccopen back to where it was with the parsers? This is a breaking API
> >> change (affects GaussSum for example), and also, it seems
> >> unneccessary. This might be a simplification but everything in io is
> >> for writing, everything in parsers is for reading (unless I've missed
> >> something).
> >>
> >> I can workaround myself, as I bundle cclib with the Windows GaussSum,
> >> but the Linux distros versions use the system one so ideally the cclib
> >> library version should be bumped to 2.0.
> >>
> >> Regards,
> >> - Noel
> >>
> >>
> >> ------------------------------------------------------------
> ------------------
> >> Check out the vibrant tech community on one of the world's most
> >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> >> _______________________________________________
> >> cclib-devel mailing list
> >> ccl...@li...
> >> https://lists.sourceforge.net/lists/listinfo/cclib-devel
> >
> >
>