Standard logging facility

Alexander_Kolov · December 3, 2015, 11:43pm

Hi all,

Are the any plans on implementing standard logging API, akin to Python’s logging facility?
I believe it would be vastly beneficial if provided by a core library.

Cheers,
Alex

Tony_Parker · December 4, 2015, 3:17am

Hi Alex,

Right now we’re staying focused on the 3 libraries released today (certainly lots left to do there!), but I think there is room to think about additional functionality that belongs in the core libraries in the future. Logging is certainly an area where there are a lot of opinions about the "right way", so I imagine it would be quite a project to invent something in this area that meets the needs of most projects.

Thanks,
- Tony

···

On Dec 3, 2015, at 3:43 PM, Alexander Kolov <me@alexkolov.com> wrote:

Hi all,

Are the any plans on implementing standard logging API, akin to Python’s logging facility?
I believe it would be vastly beneficial if provided by a core library.

Cheers,
Alex

_______________________________________________
swift-corelibs-dev mailing list
swift-corelibs-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-corelibs-dev

Alexander_Kolov · December 5, 2015, 6:49pm

Revisiting this again, I’d like to start gathering some options and prepare to work on some implementation. At this point I’m leaning towards python logging (https://docs.python.org/3.6/library/logging.html\) and even structlog (http://structlog.readthedocs.org) APIs as a starting point.
So hearing any opinions and input would be greatly appreciated!

Regards,
Alex

···

On Dec 4, 2015, at 4:17 AM, Tony Parker <anthony.parker@apple.com> wrote:

Hi Alex,

Right now we’re staying focused on the 3 libraries released today (certainly lots left to do there!), but I think there is room to think about additional functionality that belongs in the core libraries in the future. Logging is certainly an area where there are a lot of opinions about the "right way", so I imagine it would be quite a project to invent something in this area that meets the needs of most projects.

Thanks,
- Tony

On Dec 3, 2015, at 3:43 PM, Alexander Kolov <me@alexkolov.com> wrote:

Hi all,

Are the any plans on implementing standard logging API, akin to Python’s logging facility?
I believe it would be vastly beneficial if provided by a core library.

Cheers,
Alex

_______________________________________________
swift-corelibs-dev mailing list
swift-corelibs-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-corelibs-dev

Tony_Parker · December 5, 2015, 6:53pm

Hi Alex,

Since logging is a fairly broad topic, and would result in new API, I think we should follow the Swift evolution process for this idea. Check out the process here:

github.com

apple/swift-evolution/blob/main/process.md

# Swift Evolution Process

Swift is a powerful and intuitive programming language that is designed to make writing and maintaining correct programs easier. Swift is growing and evolving, guided by a community-driven process referred to as the Swift evolution process, maintained by the [Language Steering Group][language-steering-group]. This document outlines the Swift evolution process and how a feature grows from a rough idea into something that can improve the Swift development experience for millions of programmers.

## Scope

The Swift evolution process covers all design changes, no matter how small, to the Swift language, its standard library, and the core tools necessary to build Swift programs.  This includes additions, removals, and changes to:
- the features of the Swift language,
- the public interface of the Swift standard library,
- the configuration of the Swift compiler, and
- the core tools of the Swift package ecosystem, including the configuration of the [Swift package manager](https://www.swift.org/package-manager/) and the design of its manifest files.

The design of other tools, such as IDEs, debuggers, and documentation generators, is not covered by the evolution process.  The Core Team may create workgroups to guide and make recommendations about the development of these tools, but the output of those workgroups is not reviewed.

The evolution process does not cover experimental features, which can be added, changed, or removed at any time.  Implementors should take steps to prevent the accidental use of experimental features, such as by enabling them only under explicitly experimental options.  Features should not be allowed to remain perpetually experimental; a feature with no clear path for development into an official feature should be removed.

Changes such as bug fixes, optimizations, or diagnostic improvements can be contributed via the normal contribution process; see [Contributing to Swift](https://www.swift.org/contributing/).  Some bug fixes are effectively substantial changes to the design, even if they're just making the implementation match the official documentation; whether such a change requires evolution review is up to the appropriate evolution workgroup.

Which parts of the Swift project are covered by the evolution process is ultimately up to the judgment of the Core Team.

This file has been truncated. show original

It’ll be important to discuss this on the swift-evolution list as well.

Thanks,
- Tony

···

On Dec 5, 2015, at 10:49 AM, Alexander Kolov <me@alexkolov.com> wrote:

Revisiting this again, I’d like to start gathering some options and prepare to work on some implementation. At this point I’m leaning towards python logging (https://docs.python.org/3.6/library/logging.html\) and even structlog (http://structlog.readthedocs.org) APIs as a starting point.
So hearing any opinions and input would be greatly appreciated!

Regards,
Alex

On Dec 4, 2015, at 4:17 AM, Tony Parker <anthony.parker@apple.com> wrote:

Hi Alex,

Right now we’re staying focused on the 3 libraries released today (certainly lots left to do there!), but I think there is room to think about additional functionality that belongs in the core libraries in the future. Logging is certainly an area where there are a lot of opinions about the "right way", so I imagine it would be quite a project to invent something in this area that meets the needs of most projects.

Thanks,
- Tony

On Dec 3, 2015, at 3:43 PM, Alexander Kolov <me@alexkolov.com> wrote:

Hi all,

Are the any plans on implementing standard logging API, akin to Python’s logging facility?
I believe it would be vastly beneficial if provided by a core library.

Cheers,
Alex

_______________________________________________
swift-corelibs-dev mailing list
swift-corelibs-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-corelibs-dev